View MB86960APF-G_3296697.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

features ? high-performance packet buffer architecture pipe- lines data for highest throughput ? 20 mbyte/second data transfer rate to/from the system bus ? on-chip buffer controller manages pointers, reduces software overhead ? efficient, configurable two bank transmit buffer and ring receive buffer ? bus-compatible with most popular microprocessors, including risc ? complies with international standards for ethernet, iso/ansi/ieee 8802-3 ? high-speed burst and single transfer dma ? 64-element hash table for multicast address filtering ? high-speed, low-power cmos technology ? power down mode reduces power dissipation for battery-powered equipment ? available in 100-pin plastic quad flat package general description the mb86960 network interface controller with encoder/decoder (nice ? ) is a high-performance, highly integrated monolithic device which incorporates both network controller, complete with buffer manage- ment, and manchester encoder/decoder. it allows implementation of a 7-chip solution for an ethernet interface when used with either of fujitsu's bus interface chips, the mb86953 for pc/xt/at or the mb86954 for micro channel ? , and either of fujitsu's transceiver chips, the mbl8392a coaxial transceiver or mb86962 10base-t twisted-pair transceiver. the unique buffer management architecture of the mb86960 allows packet data to access a buffer memory area from the host and from the network media simultaneously, with virtually no interaction. the network controller updates all receive and transmit pointers internally, thus reducing the software overhead required to control these operations, resulting in superior benchmark speed and application performance. the nice device has a partitionable 2, 4, 8, or 16 kilobyte, two-bank, transmit buffer which allows multiple data packets to be achainedo together and transmitted to the network from a single transmit command, thus allowing greater design flexibility and throughput. receive packets are captured in a ring buffer which can be configured in various sizes from 4 to 62 kilobytes, depending on memory equipped and amount used for the transmit buffer. possible configurations for the system bus interface include i/o mapping, memory mapping and dma access, or a combination of these. with a 20 mbyte/sec bandwidth, the nice system bus interface allows you to use the full throughput capacity of its unique packet buffering architecture. the nice controller's selectable bus modes provide both big- and little-endian byte ordering, permitting an efficient data interface with most microprocessors and higher-level protocols. implemented in fujitsu's high-speed, low-power cmos process, the mb86960 is supplied in a 100-pin plastic quad flat package for surface mounting. pin configuration 31 50 80 51 100 81 1 30 100pin plastic quad flat pack (pqfp) top view april1993 data sheet mb86960 network interface controller with encoder/decoder (nice)
mb86960 pin assignments and descriptions supplied in a 100-pin plastic quad flat pack, the nice controller presents a small foot-print to the board design, and is surface-mountable with its gull-wing leads. see pin configuration and pin assignments for the pin numbering. 26 dreq o 27 dack i 28 v cc e 29 rd i 30 we i 31 reset i 32 bd0 b 33 bd1 b 34 bd2 b 35 bd3 b 36 bd4 b 37 bd5 b 38 bd6 b 39 bd7 b 40 gnd e 41 bd8 b 42 bd9 b 43 bd10 b 44 bd11 b 45 bd12 b 46 bd13 b 47 bd14 b 48 bd15 b 49 boe o 50 bwe o 1 sd11 b 2 sd10 b 3v cc e 4 gnd e 5 sd9 b 6 sd8 b 7cs i 8 bhe i 9 sw/sb o 10 sa0 i 11 sa1 i 12 sa2 i 13 sa3 i 14 rdy (rdy) o 15 gnd e 16 sd0 b 17 sd1 b 18 sd2 b 19 sd3 b 20 sd4 b 21 sd5 b 22 sd6 b 23 sd7 b 24 eop (eop) i 25 int o pin no. pin name type 51 bcs0 o 52 bcs1 o 53 v cc e 54 ba0 o 55 ba1 o 56 ba2 o 57 ba3 o 58 ba4 o 59 ba5 o 60 ba6 o 61 ba7 o 62 ba8 o 63 ba9 o 64 ba10 o 65 gnd e 66 ba11 o 67 ba12 o 68 ba13 o 69 ba14 o 70 ba15 o 71 ten b 72 txd b 73 gnd e 74 txdata o 75 txdata+ o note: dual function pins have two names with the second in parentheses ( ). b = bidirectional i/o i = standard input o = totem pole output pin no. pin name type pin no. pin name type 76 x1 i 77 x2 o 78 v cc e 79 gnd e 80 tck b 81 rxdata i 82 rxdata+ i 83 col i 84 col+ i 85 v cc e 86 lbc b 87 ac/dc i 88 rck b 89 ckout o 90 gnd e 91 rxd b 92 col b 93 crs b 94 rdypol i 95 cntrl o 96 rmt o 97 sd15 b 98 sd14 b 99 sd13 b 100 sd12 b pin no. pin name type pin assignments
mb86960 block diagram buffer port registers status & control registers hash table read/write dma system interface sw/sb rmt cntrl reset rdypol rdy (rdy) int eop (eop) dreq dack cs we rd bhe sd00 sa0 col crs rck rxd lbc ten tck txd x1 x2 ac/dc col+ col rxdata+ buffer controlller receiver manchester encoder/ decoder transmitter network controller bsc1 bcs0 bd0 bd15 ba0 ba15 bwe boe control sa3 sd15 control internal address bus internal data bus rxdata txdata+ txdata rx data tx data ckout
mb86960 pin descriptions system bus interface pins symbol type description reset i hardware reset: active high. a minimum pulse of 300 nanoseconds in duration is required. this pin resets nice's internal pointers and registers to the appropriate state. note: nice must be reset after power start before using. rdy (rdy) o ready: this output is asserted to indicate to the host that nice is ready to complete the requested read of write operation. it will also be asserted if the device is unable to respond to the request for a read or write within 2.4 microsecond, in that case, nice will also assert int and the bus read error status bit, dlcr1<6>, or bus write error status bit dlcr<0>. rdy (rdy) may be an active low or active high signal as determined by rdypol, pin 94. if rdypol is a a1o, rdy (rdy) will be active high. if rdypol is tied to a a0o rdy (rdy) will be an active low signal. rdypol i ready polarity select: control input to select the polarity of rdy (rdy), pin 14. when this pin is tied high, rdy (rdy) will be active high. if rdypol is tied low, rdy (rdy) will be an active low signal. we i write: the we pin is an active low input that enables a write operation form the host system to the buffer memory port or to internal registers selected by system address inputs sa0-3. rd i read: active low input specifies that the current transfer between nice and the host system is a read from one of nice's internal registers or its data port as selected by sa0-3. cs i chip select: this active low input signal is the chip select for nice. bhe i byte high enable: active low. this is the byte/word control line. it is used only when nice is configured for a 16-bit data bus by the sb/sw bit of dlcr6. it allows word, upper byte only or lower byte only transfers. the address select pin sa0 is used with bhe for byte or word transfers. as follows. sb/sw bhe sa0 function 0 0 0 word transfer 0 0 1 byte transfer on upper half of data bus (sd15-8) 0 1 0 byte transfer on lower half of data bus (sd7-0) 0 1 1 reserved 1 x x byte transfer (sd7-0) int o interrupt: active low. indicates that nice requires host system attention after successful transmission or reception of a packet, or if any error condition occur, if an eop (end of process) signal from the host occurs after the completion of the dma cycle. the interrupt signal is maskable and can be disabled by writing a 0 to the appropriate mask bit. eop (eop) i end of process: indicates to nice that the dma transfer is finished. when the host dma controller asserts eop (eop), further assertion of nice's bus request output. dreq, will be discontinued. note: dual function pins have two names with the second in parentheses ( ). b = bidirectional i/o i = standard input o = totem pole output
mb86960 pin descriptions system bus interface pins (continued) symbol type description cntrl o control: this pin is the complement of the register bit cntrl, dlcr4<2>. it is used to control external functions. rmt o remote control packet: when dlcr5<2> is set high, this pin follows the rmt 0900h bit (dclr1<4>) which indicates that a complete special packet with type field= 0900h has been received. this is intended for use as a remotely-controlled hardware function from other nodes in the network. dreq o dma request: issued to the dma controller to indicate that nice has data available to be read in its receive buffer, of is ready to accept data into its transmit buffer. dack i dma acknowledge: active low, indicate that the dma controller is ready to transfer data between the host system and nice's buffer memory through bmpr8. sa<3:0> i system address lines: specify which of the internal registers of ports of nice is selected for read/write operations. sd<15:0> b system data bus: all data, command and status transfers between the host system and nice take place over the bidirectional, 3-state, bus. the direction of the transfer is controlled by rd and we . the register or buffer port being accessed is selected by a combination of dack (if active, selecting the buffer port), of the address pins sa3-0 and register bank select bits reg bank 1 and reg bank 0, dlcr7<3:2>. the portion of the data bus over which the transaction occurs is controlled by sb/sw, bhe , and sa0. sw/sb o system word/system byte configuration: this signal output reflects the inverse of dclr6<5>, sb/sw. if sw/sb=1, the system interface is configured for word transfers, if sw/sb=0, the system interface is configured for byte-wide transfer on sd7-0, the lower byte. note: dual function pins have two names with the second in parentheses ( ). b = bidirectional i/o i = standard input o = totem pole output
mb86960 pin descriptions buffer memory interface pins symbol type description bcs0 o buffer chip select: bcs1 and bsc0 are the chip select lines, most significant byte and least bcs0 bsc1 o o buffer chip select : bcs1 and bsc0 are the chip select lines , most significant byte and least significant byte respectively, of the dedicated buffer srams, active low. boe o buffer output enable: this active low signal is the output enable for the buffer sram, and is asserted by nice during buffer memory read cycles. bwe o buffer write enable: active low. used as a write strobe to the buffer sram memory during write operations. bd<15:0> b b buffer data: data lines between the sram buffer memory and nice. this sram data bus is configurable for an 8-bit or 16-bit data size by buffer byte/buffer word, bb/bw, in b configurable for an 8 - bit or 16 - bit data size by buffer byte/buffer word , bb/bw , in dlcr6<4>. the transfer byte order within a word, most significant or least-significant byte first, is determined by data_order, dlcr7<1>. ba<15:0> o o buffer address: these lines address up to 64 kilobytes of sram buffer memory. network interface pins symbol type description txdata+ o transmit interface pair: these are the differential outputs to the transceiver for transmitting. txdata+ txdata o o transmit interf ace p air: these are the dif ferential outputs to the transceiver for transmitting . rxdata+ i received data: these are the manchester differential inputs from the transceiver to the receiver. rxdata+ rxdata i i received da ta: these are the manchester dif ferential inputs from the transceiver to the receiver . col+ col i i collision: these differential inputs are driven with a 10 mhz signal when the transceiver detects a collision on the media. ac/dc i ac/dc coupling select: ac/dc = 1 selects ac coupling; 0 selects dc coupling for the txdata outputs. when ac coupling is selected, both txdata+ and txdata are driven to the same output voltage level during the transmit idle period to prevent saturation of the isolation transformer. with dc coupling, these outputs remain at a 1 level during idle periods. system clock pins symbol type description x1 i crystal input: connection for one side of the 20 mhz crystal, or input for an external 20 mhz clock source. x2 o crystal output: connection for the other side of the 20 mhz crystal. leave unconnected if an external clock is used. ckout o clock output: 20 mhz free-running clock output provided by the crystal oscillator circuit.
mb86960 pin descriptions the following eight pins are provided for optional connection to an external encoder/decoder. they can also be used for test purposes, but are not used in a typical network interface application. special encoder/decoder modes are selected by setting dlcr7<7:6>. refer to the medium connection section under system configuration for a complete description of these modes. controller e encoder/decoder interface pins symbol type description txd b transmit data: nrz transmit serial data. normally not used. in aencoder/decoder bypasso mode and anice + monitoro mode, an output which can be fed to an external encoder. in aencoder/decoder testo mode, an input to the on-chip encoder. tck b transmit data clock: clock synchronous with txd serial data. normally not used. in aencoder/decoder bypasso mode, a 10 mhz data clock input used by the controller to synchronize the txd data signal. in anice + monitoro mode and aencoder/decoder testo mode, an output from the on-chip encoder. ten b transmit enable: normally not used. in anice + monitoro mode and aencoder/decoder bypasso mode, this pin is an output which can be used to control an external encoder. when asserted high, ten enables the encoding of the transmitted data. in aencoder/decoder testo mode, an input to the on-chip encoder. col b collision presence: normally not used. in aencoder/decoder bypasso mode, an active low input which indicates that the collision inputs col are active, signifying that the transceiver has detected a collision on the media. in anice + monitoro mode and aencoder/decoder testo mode, this is an output from the on-chip encoder/decoder section. col is a normally high input which changes to a 10 mhz pulse stream during collision detection. lbc b loopback control: normally not used. in aencoder/decoder bypasso mode and anice + monitoro mode, this output should be connected to the loopback control pin of the external encoder/decoder. when this output is asserted high, the external encoder/decoder is placed in loopback mode. ten enables the encoding of the transmitted data. in aencoder/decoder testo mode, this is an input with the same function. rxd b receive serial data: normally not used. in aencoder/decoder bypasso mode, anice + monitoro mode and aencoder/decoder testo mode, an nrz serial bit stream from a decoder or demodulator to the data link controller. rck b receive data clock: normally not used. in aencoder/decoder bypasso mode, anice + monitoro mode and aencoder/decoder testo mode, this pin is an input for the serial data clock as recovered by the external decoder or demodulator. crs b carrier sense: normally not used. in aencoder/decoder bypasso mode, an input indicating the presence of incoming data on the network. in anice + monitoro mode and aencoder/decoder testo mode, an output from the on-chip encoder/decoder. assertion of this active high input indicates that a carrier has been sensed at the rxdata inputs.
mb86960 pin descriptions mode configuration and encoder/decoder pin input/output table cnf1 cnf0 mode txd tck ten lbc rxd rck crs col 0 0 normal nice internal e/d is used with nice controller, no signal appears on pins none none none none none none none none 0 1 nice + monitor internal e/d is used with nice controller, signal appears on output o o o o o o o o 1 0 e/d bypass external e/d is used with nice controller, internal e/d is shutdown o i o o i i i i 1 1 e/d test internal e/d is used only, nice controller section is shutdown i o i i o o o o device power pins symbol description v cc power supply: a +5 v dc 5% supply is required. gnd system ground: ordering code package style package code ordering code 100-pin plastic quad flat pack fpt-100pm01 mb86960apfg
mb86960 system configuration a highly integrated system configuration can be achieved with the nice controller. figure 1 illustrates a low chip count lan controller with nice, a bus interface chip such as fujitsu's mb86953 or mb86954, and either a coaxial transceiver such as fujitsu's mbl8392a or a 10base-t twisted pair transceiver such as fujitsu's mb86962. because of its high integration and unique, innovative architecture, which handles all aspects of packet management and storage, a local microprocessor is not required. the nice controller connects to the host system bus to provide command and status interfaces as well as packet data access. command and status registers can be directly accessed by the host processor when mapped into the i/o or memory space of the host. through a port on the device, data packets to be transmitted to the media are transferred first from host memory to a dedicated buffer memory for temporary storage until transmitted. received data packets are first stored in the buffer memory, then later transferred to the host memory. host cpu main memory mb86960 nice buffer memory lan network medium aui system bus mb86953 pc or mb86954 mca bus interface mbl8392a coaxial or mb86962 10baset transceiver figure 1.typical system configuration medium connection connection to the lan medium can be accomplished with any of the popular connection methods: 1) on-board connection to unshielded twisted pair through a 10base-t transceiver, 2) on-board connection to a thin 50-ohm coaxial cable through a 10base2 transceiver or 3) off-board connection to any other type of medium, such as standard ethernet coaxial cable (10base5), through an attachment unit interface (aui) connector. nice has an encoder/decoder (e/d) on chip. an external encoder/decoder can be used by making the nice chip act like a controller alone (depending on customer's needs). this option can be changed by using bits 7 and 6 of dlcr7. eight pins related to the on-chip e/d can be configured by dlcr7<7:6> (register dlcr7, bits 7 through 6) to operate in one of four modes. these pins are txd, tck, ten, lbc, rxd, rck, crs, and col . in the anormal niceo mode, an internal e/d is used. in this mode, the pins are all electrically isolated and no signals appear on the pins. in anice + monitoro mode, all the pins listed above are outputs whose specific signals appear on the pins and can be monitored externally. in aencoder/de- coder bypasso mode, an external encoder/decoder is used with the nice controller, its own internal e/d is shut down. in this mode, the pins are either outputs or inputs as needed to control the external encoder/decoder. in the aencoder/decoder testo mode, only the e/d on nice is active and accessible, the nice controller section is shut down. in this mode, the pins are outputs or inputs for an encoder/decoder, with the opposite control direction of the outputs or inputs in the aencoder/decoder bypasso mode. the various possibilities are shown in figure 2 and the table below. dlcr7 bit 7 dlcr7 bit 6 function 0 0 normal nice 0 1 nice plus monitor 1 0 encoder/decoder bypass 1 1 encoder/decoder test
mb86960 controller encoder/ decoder nice case 00: normal nice mode controller encoder/ decoder nice case 01: nice + monitor controller encoder/ decoder nice case 10: encoder/decoder bypass controller encoder/ decoder nice case 01: nice + monitor controller test eed test rxd, rxc crs, tck, col ten, txd, lbc figure 2. encoder/decoder modes crystal oscillator the iso/ansi/ieee 88023 international lan stan- dard specifies a bit clock rate of 10 mbit/sec. this is obtained from a 20 mhz clock generated by the on-chip oscillator, which operates from an external crystal connected between pins x1 and x2 on the nice chip. crystal capacitance as specified by the manufacturer should be connected from x1 and x2 to ground, considering any stray capacitance which can vary the crystal's frequency. see figure 3 for typical values. a crystal with the following specifications is recom- mended: quartz (at-cut; 20 mhz; frequency/accuracy of 50 ppm at 25 c to 70 c; parallel resonant with 20 pf load in a fundamental mode. possible vendors include: ecliptek corp. (costa mesa, ca), p/n ecsm200-20.000; and m-tron industries, inc. (yank- ton, sd), p/n mp-1 & mp-2, with 20mhz, 50ppm over 0 c to 70 c, and 18 pf fundamental load. nice x1 x2 20 mhz 18 pf 18 pf figure 3. crystal connection the clock also serves as a reference for an internal phase locked loop which is used for clock recovery in the decoder section. internal clocks are shut down when dlcr7 bit 5, pwrdn , is invoked for power down mode. sram configurations eight different configurations of sram for the packet buffer are possible as illustrated in figure 4. first, the width of the sram data path can be 8 or 16 bits, selected by programming the buffer byte/buffer word (bb/bw) bit, bit 4 of dlcr6. if this bit is set to 1, byte-wide data is selected; if set to 0, the width is word-wide (16 bits). the sb/sw bit, dlcr6 bit 5, selects the system bus width, while the bb/bw bit, dlcr6 bit 4 selects the sram buffer width. secondly, the depth of the sram is programmed by setting buffer size 1 and 0 (bs1 and bs0), bits 1 and 0 in dlcr6. depth selections are 8, 16, 32 or 64 kilobytes.
mb86960 8kx8 8kx8 bcs1 bcs0 bd<7:0> bd<15:8> 8 8 ba<13:1> 8kx8 8kx8 bcs1 bcs0 bd<7:0> 8 ba<13:1> 4kx8 4kx8 bcs1 bcs0 bd<7:0> bd<15:8> 8 8 ba<12:1> 8kx8 bcs0 bd<7:0> 8 ba<12:0> 32kx8 32kx8 bcs1 bcs0 bd<7:0> bd<15:8> 8 8 ba<15:1> 32kx8 32kx8 bcs1 bcs0 bd<7:0> 8 ba<15:1> 16kx8 16kx8 bcs1 bcs0 bd<7:0> bd<15:8> 8 8 ba<14:1> 32kx8 bcs0 bd<7:0> 8 ba<14:0> bs1 dlcr6<1> bs0 dlcr<0> 8bit buffer bus 16bit buffer bus 00 01 10 11 figure 4. sram configuration
mb86960 sb/sw bb/bw system buffer 0 0 word word 0 1 word byte 1 0 do not use 1 1 byte byte functional description the mb86960 combines the functions of an ethernet network controller with packet buffer management, and a 10 mbit/s manchester encoder/decoder. it consists of four major functional blocks: buffer controller, system interface, transmit controller with manchester encoder, and receive controller with manchester decoder. the receive and transmit sections of the chip fully implement the iso/ansi/ieee 8802-3 csma/cd specification for 10 mbit/sec ethernet. the transmitter assembles data packets for transmission and the receiver disassembles received data packets. automatic genera- tion and stripping of the 64-bit preamble, and generation and checking of the 32-bit crc are provided on-chip. other network functions provided on-chip include collision resolution by binary exponential backoff and re-transmission, several modes of address recognition, error detection and reporting, and serial/parallel and parallel/serial conversions. buffer controller the mb86960 uses a dedicated buffer memory as shown in for intermediate storage of data packets to be transmitted, and of data packets received from the network. the buffer memory is connected directly to the controller rather than to a separate local microprocessor bus, thus eliminating the need for a local microprocessor. the buffer controller keeps track of buffer memory partitioning, allocation and updating of all receive and transmit pointers automatically, thus eliminating this task from software overhead. as a result of this automation and its high-performance packet buffering, the nice controller can typically win benchmark performance tests over competing controllers. access to the buffer memory is managed by nice's on-chip buffer controller. as required, it updates internal address pointers for the tasks of transmit, retransmit, receive, rejection of packets with errors and data transfers to and from the host. thus the host is relieved of buffer management functions, making nice easy to operate and substantially reducing software requirements. packets with errors, such as crc errors, are auto matically rejected by nice unless the host asserts the aaccept bad packetso bit. when this bit is asserted, any packets received with alignment, crc or short length errors are passed on to the host processor, and the appropriate error status bits are set to inform the host of the error. similarly, by setting the aaccept short packetso bit, reception of short packets down to 6 bytes in length is allowed. (normal operation requires an ieee minimum length packet of 60 bytes, excluding preamble and crc.)
mb86960 currently available free buffer area receive buffer ring 62 kbytes max transmit buffers received packet n + 3 (last part) received packet n + 3 (first part) received packet n received packet n + 1 received packet n + 2 one or two transmit buffers notes 1. length (l) = 8, 16, 32, or 64 kbytes. 2. transmit size (t) = 2 (one bank), 4 (two banks), 8 (two banks), or 16 (two banks) kbytes. 3. receive packets are aligned on an eight byte boundary . 4. each received packet is preceded by a four byte packet header as follows: byte 0 packet status byte 1 not used byte 2 packet size lsb's byte 3 packet size msb's t l figure 5. buffer memory organization as shown in the buffer memory is divided into transmit and receive buffer areas. the partitioning of the memory is programmable, allowing the system to be configured with different proportions of space available for the transmitter and receiver functions. by programming the proportions, an optimum usage of the memory can be selected, according to the demands of a particular application. the section of the memory used by the transmitter can be configured as a single buffer 2 kilobytes long, or as a pair of banks, each either 2, 4 or 8 kilobytes long. within each buffer or bank, one or more packets can be written by the system until the available space is too small for another packet. once started, the transmitter will transmit all packets in the buffer automatically before finishing with a status update, and an interrupt if so enabled. with the two-bank configurations, one bank can be transmitted while the other is being loaded. using dual buffers and loading multiple packets for apacket chainingo gives the highest rate of transmission. this will boost performance for systems that require high throughput transmission. nice can be configured to operate with 8, 16, 32 or 64 kilobytes of total buffer memory size, including both transmit and receive spaces. this memory partitioning into transmit and receive sections is allocated by the system software. the total size of the transmit buffer space can be either 2, 4, 8 or 16 kilobytes. immediately following the transmit buffer space is the receive buffer space, using the balance of the available memory.
mb86960 bank 0 62 kbytes 2 kbytes transmit section 2 kbytes 62 kbytes receive section bank 0 60 kbytes 4 kbytes transmit section 2 kbytes 60 kbytes receive section 2 kbytes bank 1 bank 0 56 kbytes 8 kbytes transmit section 4 kbytes 56 kbytes receive section bank 1 4 kbytes bank 0 48 kbytes 16 kbytes transmit section 48 kbytes receive section bank 1 8 kbytes 8 kbytes figure 6. transmit buffer
mb86960 as shown in figure 6, the remaining memory not used for the transmitter is used for the receiver, and is automatically configured as a aring buffero by the chip. packets are stored head-to-toe in the receive buffer, as they are in the transmit buffer. as packets are being stored in the receive buffer, as the end of the linear addressing space is reached, the chip's receive-write pointer automatically wraps around to the top of the receive addressing range to make a seamless ring. the receive-read pointer does the same as the packets are read out to the system. the mb86960 provides all the necessary buffer pointer management functions automat- ically, relieving the host system and its drivers of this time-consuming task. since these tasks can be done faster in hardware than in software, this not only off-loads the host system, but it also speeds up the communication processes giving higher throughput. the buffer controller automatically prioritizes and services requests for access to the memory from the transmitter, the receiver, and the host system. it updates all buffer memory pointers, allocates memory space for incoming data packets, and controls pertinent bits within the status registers providing complete packet manage- ment functions. read and/or write network media interleave data host cpu nice buffer dedicated system interface controller buffer memory transmit and simultaneous receive figure 7. simultaneous operations and buffer control capability of nice the nice chip's arbitration mechanism provides packet management by interleaving packet data accesses to the buffer memory so that the operation appears to be asimultaneouso: data can be written to or read from the buffer memory by the host via buffer memory port register 8 (bmpr8), while data packets are read out for transmission and/or written in for storage by the receiver. each interface, whether host system or network access, appears to be served independently by the controller. each interface has an associated fifo to provide time for the buffer interleaving. thus, packet data is apipelinedo through the system for highest performance and throughput, and the buffer controller supports all the cases of asimultaneouso access to the buffer memory, as illustrated in figure 7 and as follows: 1. data from the network is stored in the receive buffer. 2. the host retrieves packets from the receive buffer. 3. the host loads packet data into the transmit buffer. 4. the transmitter obtains data for transmission from the transmit buffer. 5. any combination of the above can occur concurrently, including all four at once. system access to buffer nice supports both programmed i/o, single cycle dma and burst mode dma transfers between the buffer memory and the host system. the host accesses the buffer memory by reading from or writing to nice's buffer memory port register 8 (bmpr8). data being read or written by the system passes through on-chip fifo's to eliminate the effects of real-time interaction between the system, the transmitter and the receiver as they all access the buffer memory. all read and write operations to the external sram memory are controlled automatically by the nice chip.
mb86960 transmitter access to buffer the size of each of the transmit banks can be changed by programming the buffer size control bits, bs0 and bs1. the transmit buffer size is thus allocatable by the software to be a single 2-kilobyte transmit buffer, two 2-kilobyte transmit buffers, two 4-kilobyte transmit buffers, or two 8 kilobyte transmit buffers. in all configurations, a single packet or multiple packets can be loaded into the buffer at one time for transmission. when a single transmit buffer is used, the system and the transmitter time-share the use of the buffer. when two buffers are used, the system can load packets into one of the buffers while the contents of the other are being transmitted. at reset, the pointers are initialized to point to the beginning of one of the transmit buffers. each time the host writes data to the buffer via the buffer memory port register, an internal pointer is advanced to the next memory location within the transmit buffer. once a data byte/word is written, it cannot be read and the internal pointer cannot be reversed. internal pointers managed by nice control which of the two banks is selected for access by the host and which byte/word of the bank is accessed. nice will switch banks as soon as the transmit start bit (tx start) of bmpr10 is written high by the host system. when this occurs, nice will start transmitting at the earliest opportunity. another automatically-managed pointer, the transmit-read pointer sequences through the bank being transmitted to read the packet data into the transmitter through its fifo. if a collision occurs, the packet will be automatically retransmitted after a pseudo-random waiting interval called the backoff interval. if there are multiple packets in the bank, nice will continue down the list, automatically transmitting them all. the details of this operation are described in the section on packet transmission. nice has the capability to transmit multiple back-to- back packets of varying legal ethernet sizes to the lan network. these packets may vary in length from 60 bytes to 1,514 bytes, excluding preamble and crc fields. as shown in figure 8, multiple packets can reside within one transmit bank, separated by a non-transmitted, two-byte header which provides the length of the packet in bytes. upon reaching the end of the alisto or achaino of packets, the transmitter will stop, update it's status bits and, if enabled, generate an interrupt. transmit packet data formats the packets to be transmitted, less preamble and crc fields, are first loaded into the transmit buffer along with a two-byte header indicating the packet length in bytes. see figure 8 for details. multiple packets can be loaded at the same time provided there is room in the buffer. after the packets are loaded, the host initiates transmission by writing the number of packets just loaded into a register for this purpose on the chip. if the two-bank buffer configuration has been selected, the second bank can now be loaded with additional packets. packet 1 length lsb length msb packet 2 data 1 length lsb length msb data 2 length lsb length msb data 3 length lsb length msb data 4 data n unused buffer area figure 8. transmit buffer detail
mb86960 receiver access to buffer once initialized and enabled, the receiver will automati- cally load any error-free incoming packets which pass the address filter into the receive buffer through an on-chip fifo, appending a four-byte header to the front end which provides packet length and status. an interrupt can be provided to alert the host processor that a packet is available in the buffer. the host processor can read out receive packets as they become available. continuous reception can continue as long as the receive buffer does not become full. if the host processor reads the receive packets from the buffer promptly, the buffer will not fill up. but if overflow does occur, an interrupt will be generated to indicate the problem. if this occurs, data should be read from the buffer to free space. as soon as space becomes available in the receive buffer, the receiver will automatically continue reception. the receive buffer size can vary between a maximum of 62 kilobytes when 2 kilobytes is allocated for the transmit section and maximum memory size of 64 kilobytes is used, to a minimum of 4 kilobytes if 4 kilobytes is allocated for the transmit section and minimum memory size of 8 kilobytes is used. the receive section dynamically allocates space for each individual incoming data packet along an eight-byte apageo boundary. each received packet is preceded by a four byte header which provides packet status and the length of that data packet. the data packets are linked or achainedo by internal pointers which use the length value in the packet header to calculate the length of the packet, and the starting address of the next packet. this buffer format is shown in figure 9. since nice controls its dedicated buffer memory, fifo size and depth are unimportant in this architecture, and need not be considered in system timing considerations. a status bit in one of nice's internal registers (rx buf empty) informs the host when one or more packets are resident in the receive buffer and available to be read. the host retrieves these packets from the buffer memory by successive reads of bmpr8. once a data byte/word is read from the buffer memory, internal pointers are advanced to the next byte/word. as data is thus read by the system, that memory becomes available for reception of new packets. nice automatically rejects an incoming packet if there is not enough buffer space to fully receive that packet. therefore, there is no chance for packets already received to be aoverruno by incoming packets. when dlcr5<5>, the acpt bad pkts (aaccept bad packetso) bit is set to a a0o (disabled), a bad incoming packet causes nice to release buffer space in which that packet is contained and reset its internal pointers so as to use that space for the next incoming packet. if this bit is set to a a1o, the packet with a short length, alignment or crc error will be accepted and the appropriate error bits in the status field of its header will be set. the same applies to dlcr5<3>, acpt short pkts, which when high allows retention of packets below 60 bytes in length, excluding preamble and crc (shorter than ieee 802.3 minimum size). packet n1 status reserved data length lsb length msb data data unused buffer area status reserved length lsb length msb status reserved length lsb length msb data packet n figure 9. receive buffer detail
mb86960 receive packet data formats receive packets, less preamble and crc fields, are stored in the buffer along with a four-byte header. the first byte gives status information, indicating errors, if any, that occurred during reception of the packet. normally packets with errors are automatically discarded and eliminated from memory by the chip, but with a mode selection, the chip can allow reception of bad packets, with indication of their errors in the status byte of the header. the second byte of the header is reserved for possible future use. the last two bytes of the header give the byte count of the packet, less preamble and crc. refer to figure 9. system interface the system interface block provides the connection between nice and the host cpu. nice supports both 8-bit and 16-bit bus widths and byte or word transfers as determined by dlcr6<5>, sb/sw, the asystem byte or system wordo configuration bit. depending on the type of host cpu, nice will supply the data order, msb or lsb first according to the setting of dclr7<0> as described in the detailed register descriptions. nice supports i/o-mapping, memory mapping, and burst or single transfer dma modes. an interrupt output, int , is provided which may be programmed by the user to inform the cpu of transmit and receive status conditions requiring host processing. three sets of user-accessible registers are contained within the mb86960. all registers are accessible as bytes or words. register access all control and status registers on the nice chip are accessible through its bus interface port, which can be i/o or memory mapped in the system. eight of the registers in the set, whose addresses are xxx0h through xxx7h, are always directly accessible. for the remaining physical addresses, three different banks of registers can be accessed through indirect addressing of the banks (bank switching). the bank switching bits are part of the first eight registers which are permanently resident. the bank-switched register group consists of three sets or abankso of registers. one of the sets is for node id (ethernet address) and tdr diagnostics, another is the hash table for multicast address filtering, and the third is for buffer memory access. this third bank is normally selected most of the time, except during initialization or diagnostic routines, as access to the other registers is not needed during normal operation. buffer access buffer memory port register 8 (bmpr<8>) of the buffer memory port register set provides serial access to the receive and transmit buffers through on-chip fifo's. this port can be accessed with 8-bit or 16-bit wide data. there is a separate fifo for each direction of data transfer, so there is no complicated direction control needed. writes to the transmit buffer can be interleaved with reads from the receive buffer if desired. all buffer memory pointers are automatically maintained by the chip, eliminating software overhead normally needed for this. this port can be accessed with i/o instructions using register address xxx8h, or by using dma. in the latter case, assertion of the dack input is sufficient to select the port. thus data can be transferred from host memory to the transmit buffer, or from the receive buffer to host memory using cpu string moves, single-transfer programmed i/o moves, or dma. the choice should be made according to which is most efficient at a system level, taking into account that a speedy transfer process will result in the best performance. a slow transfer process may not be satisfactory because it might result in poor throughput and performance, and might allow the receive buffer to overflow, losing packets. dma operation the mb86960 supports both single cycle and burst dma operation for transfers of data between the host system and the dedicated buffer memory. the dreq and dack signals are used for handshaking between the external dma and nice. there is also an aend of processo input pin which, when asserted by the system dma controller during a transfer cycle, will terminate the dma activity after the current cycle completes. if enabled for dma interrupt, upon completion of the dma activity, the chip will generate an interrupt. usually only one dma operation will be run at a time, although the nice chip could run two interleaving operations, one reading and one writing. there is only one dma eop bit, and only one dreq pin and one dack pin, so most hosts could not support more than one dma operation at a time with nice.
mb86960 dma write (transmit) transmit dma enable, tx dma en, bmpr12<0>, is set high to enable dma operation for transfers of data packets from the host memory to nice's transmit buffer. burst transfers can also be enabled by invoking the dma burst control register bmpr13<1:0>. when nice is ready to begin to accept data from the host, nice will assert its dma request output, dreq. the host responds by asserting dma acknowledge, dack , followed by write enable, we , and placing the data on the data bus. nice will assert its rdy (rdy) output when it is ready to complete the current data transfer cycle (polarity of rdy (rdy) and eop (eop) inputs are independently programmable). nice accepts that data byte/word into its bus write fifo, and later moves it into buffer memory. at the close of a transfer cycle, the host negates we . in burst mode, nice will negate dreq two cycles before the end of the burst. the host dma will then complete the last two transfer cycles, then negate dack to close the burst. to start another burst, nice will re-assert dreq. the number of dma write cycles within one burst can be 1, 4, 8, or 12 data transfers (bytes or words) depending on the burst control bits burst1, burst0, bmpr13<1:0>. the dma controller may assert the end-of-process input, eop (eop), concurrently with the last data transfer cycle to indicate that the entire transfer process has been completed. this sets the dma eop bit in nice which causes nice to discontinue making further data requests. if enabled, the eop (eop) signal assertion can also generate an interrupt. when the dma eop bit, dlcr1<5>, is set, the int pin will assert if dlcr3<5>, interrupt enable for dma eop , is high. this interrupt can be used by the host to initiate the actions for closing the process. upon servicing the interrupt, if dma eop is high, the host should close the dma process, reset the nice chip's dma logic and clear the interrupt by writing 00h to bmpr12. note: clearing tx dma en must be done to close the transmit dma process before attempting another dma process. this is accomplished by writing 00h to bmpr12. when this is done, the dma eop bit will clear automatically, clearing the eop status and interrupt, so it is not necessary to clear the interrupt separately. after finishing the loading of packets into the buffer, the host initiates packet transmission. this is done by loading the number of packets to be transmitted into the transmit packet count register, bmpr10<6:0>, and asserting the transmit start bit, tx start, of the same register, bmpr10<7>. dma read (receive) nice will indicate when it has receive packets to be read with status bits and/or interrupts. before attempting to read a packet, the host processor first reads the rx buf empty bit, dlcr5<6>. if this bit is 0, there are one or more packets in the receive buffer to read. after reading each packet, the host will check this bit again to see if there are more. prior to beginning the transfer of a packet from nice's receive buffer to host memory via dma, the host must first read the four-byte receive packet header from the buffer to obtain the packet status and the length of the packet in bytes. calculating from the packet length the number of dma cycles needed to read the packet, the host will load that number into the cycle counter of the host dma controller. the starting address in system memory will also be loaded into the dma controller. next, rx dma en, bmpr12<1>, is set high to enable dma read operation to transfer the packet to host memory. when it is ready to begin, nice asserts its dma request output, dreq. the host responds by asserting dma acknowledge, dack , followed by read enable, rd . nice will assert its rdy output when it has placed the byte/word on the data bus and is ready to complete the data transfer cycle. the system memory will accept the data, then the host negates rd . nice shifts the data down into its bus read fifo, then moves its internal bus read pointer to point to the next byte/word in the buffer, moving it into the fifo. nice will negate dreq two cycles before the end of the burst. after the host negates dack , if nice can transfer more data, nice will re-assert dreq to repeat the process. the number of dma read cycles in a burst can be 1, 4, 8, or 12 transfer cycles of data (bytes or words), depending on the burst control bits burst1, burst0, bmpr13<1:0>. the dma controller may assert the end-of-process input, eop (eop), concurrently with the last byte/word data transfer to indicate that the entire process has completed. nice will then discontinue making further data requests. rx dma en must be cleared when the dma process is completed, and set again when the host desires to begin reading another packet from the receive buffer using dma. when eop (eop) is asserted by the host dma controller, the dma eop bit, dlcr1<5>, will be set high, and an interrupt will also be generated, provided it is enabled by a high, dlcr3<5>. this interrupt can be used by the host to initiate the final actions to close the dma process. the interrupt is cleared and the dma is disabled and reset by writing 00h to the dma enable register, bmpr12. note: clearing rx dma en must be done to close the
mb86960 receive dma process before attempting another dma process. this is accomplished by writing 00h to bmpr12. when this is done, the dma eop bit will clear automatically, clearing the eop status and interrupt, so it is not necessary to clear the interrupt separately. control and status registers the control and status registers on the nice chip are accessed through direct register addresses xxx0h through xxxfh, and indirect or bank-switching address bits rbs1, rbs0, dlcr7<3:0>. table 1 summarizes the addressing scheme. in system word mode, data can be transferred 16-bits at a time on the system bus, or 8-bits at a time by using the byte lane controls of nice. when transferring in 16-bit mode to/from the registers, even direct addresses are used to select the registers. for example, to access the transmit/receive status regis- ters, address xxx0h would be used. the transmit status would be on the low byte and the receive status on the high byte. separate access of high and low bytes is achieved by using the appropriate byte-access processor instructions. table 1. internal register address map rbs1,rbs0 sa3 sa2 sa1 sa0 address description xx xx xx xx xx xx xx xx 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 dlcr0 [1] dlcr1 dlcr2 dlcr3 dlcr4 dlcr5 dlcr6 dlcr7 transmit status receive status transmit int enable receive int enable transmit mode receive mode config 0 config 1 00 00 00 00 00 00 00 00 1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 dlcr8 dlcr9 dlcr10 dlcr11 dlcr12 dlcr13 dlcr14 dlcr15 node id 0 node id 1 node id 2 node id 3 node id 4 node id 5 tdr 0 (lsb) tdr 1 (msb) 01 01 01 01 01 01 01 01 1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 ht8 ht9 ht10 ht11 ht12 ht13 ht14 ht15 hash table 0 hash table 1 hash table 2 hash table 3 hash table 4 hash table 5 hash table 6 hash table 7 10 10 10 10 10 10 10 10 1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 bmpr8 [2] bmpr9 bmpr10 bmpr11 bmpr12 bmpr13 bmpr14 bmpr15 buffer memory port reserved transmit start 16 collisions dma enable dma burst skip packet reserved 11 x x x x e reserved 1. all registers are both word and byte accessible. in word mode, register bytes are paired to form words starting with registers 0 and 1. the odd-addressed byte becomes the high byte of the word 2. in word mode, bmpr8 is a 16-bit port. in byte mode, it is an 8-bit port. the byte ordering is determined by dlcr7<0>
mb86960 table 2. summary of control and status bits: dlcr0-7, bmpr8-15 register bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 tx status dlcr0 tx done net bsy tx-rx cr lost 0 col 16 col 0 rx status dlcr1 rx pkt bus rd err dma eop rmt 0900h short err align err crc err rx buf overflo tx int enable dlcr2 int en 0 0 0 0 int en int en 0 rx int enable dlcr3 int en int en int en int en int en int en int en int en tx mode dlcr 4 col ctr 3 col ctr 2 col ctr 1 col ctr 0 0 cntrl lbc en tx defer rx mode dlcr5 0 rx buf empty acpt bad pkts 40 bit addr acpt short pkts 1 af1 af0 config0 dlcr6 dlc en 1 sb/sw bb/bw tbs 1 tbs 0 bs 1 bs 0 config1 dlcr7 e/d cnf 1 e/d cnf 0 pwrdn rdypol rbs 1 rbs 0 eoppol m..l/ l..m buf mem port bmpr8 7 6 5 4 3 2 1 0 buf mem port bmpr9 15 14 13 12 11 10 9 8 tx start bmpr10 tx start tx pkt cnt 6 tx pkt cnt 5 tx pkt cnt 4 tx pkt cnt 3 tx pkt cnt 2 tx pkt cnt 1 tx pkt cnt 0 16 collisions bmpr11 0 0 0 0 0 16 col cntrl 2 16 col cntrl 1 16 col cntrl 0 dma enable bmpr12 0 0 0 0 0 0 rx dma enable tx dma enable dma burst bmpr13 0 0 0 0 0 0 burst 1 burst 0 skip packet bmpr14 0 0 0 0 0 skip pkt 0 0 reserved bmpr15 0 0 0 0 0 0 0 0
mb86960 table 3. summary of control and status bits:dlcr8-15, ht8-15, packet buffer headers register bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 node id 0 dlcr8 7 6 5 4 3 2 1 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . node id 5 dlcr13 47 46 45 44 43 42 41 40 tdr 0 dlcr14 7 6 5 4 3 2 1 0 tdr1 dlcr15 n/a (0) n/a (0) 13 12 11 10 9 8 hash table 0 ht8 7 6 5 4 3 2 1 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . hash table 7 ht15 63 62 61 60 59 58 57 56 tx length lsb (tx header 0) 7 6 5 4 3 2 1 0 tx length msb (tx header 1) n/a (0) n/a (0) n/a (0) n/a (0) n/a (0) 10 9 8 pkt status (rx header 0) n/a (0) n/a (0) good pkt rmt 0900h short err align err crc err rbuf ovrflo reserved (rx header 1) n/a (0) n/a (0) n/a (0) n/a (0) n/a (0) n/a (0) n/a (0) n/a (0) rx length lsb (rx header 2) 7 6 5 4 3 2 1 0 rx length msb (rx header 3) n/a (0) n/a (0) n/a (0) n/a (0) n/a (0) 10 9 8
mb86960 type descriptions (type) the following legend of descriptions applies to the type column of the register bit description tables: r: readable bit w: writeable bit c: clears associated status bit and/or interrupt when 1 is written; no effect when 0 is written n: not used; reserved; write only 0 when written 0/1:initial state after hardware reset data link control registers status and control bits for the transmitter and receiver sections of the nice chip are located in the first eight data link control registers, dlcr07. see tables 411 for details. transmit status register this register provides transmit status for the host processor. the system can enable interrupts based on the assertion (going high) of bits 7, 2, and/or 1 of this register by setting the corresponding enable bits in the transmit interrupt enable register. see table 4. bits 7, 2 and 1 in this register, the bits that can generate interrupts, are cleared by writing 1 to the bit. writing 0 to the bit has no effect, only the nice chip control logic can set these bits. clearing the bit that caused the interrupt will clear both the bit itself and the interrupt. since two or more status conditions can occur at one time, the interrupt routine must read all of them and act on all of those that are set. one method for clearing interrupts is to read the contents of the status register, then write the same value back to the register, thus clearing all bits which were set. another technique is to clear each status bit separately by writing its mask to the register. this might be done as the corresponding interrupt service is performed. note: wholesale clearing of all status bits by writing ffh to the register is not recommended, since this may clear status which has just been set and not yet read by the system. the transmitter must be idle and tx done, dlcr0<7>, must be cleared by writing 1 to it before starting the transmitter (by writing 1 to tx start, bmpr10<7>). table 4. dlcr0 e transmit status register bit symbol type description 7 tx done r c 0 transmit done: this bit is set high when all packets in the active transmit buffer have been successfully transmitted to the lan media, or skipped due to excessive collisions. can generate interrupt if enabled by dlcr2<7>. 6 net bsy r net busy: this is a real-time image of the carrier sense signal of the receiver. 5 tx-rx r 0 transmit packet received: indicates that a good packet was received by nice shortly after transmission was completed. this is used to indicate self-reception of the packet. this bit is cleared as each transmission begins. 4 cr lost r 0 carrier lost: this bit is set if the receive carrier sense input is negated during a packet transmission. this can be caused by a collision or a shorted lan medium. it is automatically cleared as each transmission begins. 3 0 n 0 reserved: write 0. 2 col r c 0 collision: this bit will assert during transmission of a data packet if a collision occurs on the network. the buffer controller will automatically retransmit the current packet after collisions up to 15 times. the user may read the number of consecutive collisions in the collision counter, dlcr4<7:4>. can generate interrupt if enabled by dlcr2<2>. 1 16 col r c 0 16 collisions: this bit is set after the sixteenth unsuccessful transmission of the same packet. can generate interrupt if enabled by dlcr2<1>. 0 0 r o reserved: write 0.
mb86960 receive status register this register contains eight status bits which can generate interrupts if enabled by the corresponding bit in dlcr3. five of these bits report the status of the most recently received packet that was accepted for storage in the receive buffer. bit 7, rx pkt, is set whenever a new packet is successfully received and stored in the buffer. one bit reports reception of a special packet with 0900h in its `type' field. other bits in this register report buffer overflow, dma end-of-process and bus read error. bits 1, 2 and 3 indicate errors, if any, detected in the packet. if acpt bad pkts, dclr5<5> and/or acpt short pkts, dlcr5<3> are set to 1 allowing acceptance of a bad packet, these error bits will be stored in the status byte of the receive packet header. if dlcr5<5> and dlcr5<3> are both 0, all packets with detected errors will be discarded automatically, and removed from the buffer. the bits in this register are cleared by writing 1 to the bit. writing 0 to the bit has no effect. only the nice chip control logic can set these bits. clearing the bit that caused the interrupt will clear both the bit itself and the interrupt. since two or more status conditions can occur at one time, the interrupt routine must read all of them and act on all of those that are set. see table 5. one method for clearing interrupts is to read the contents of the transmit and receive status registers, then write the same value back to the registers, thus clearing all bits which were set. another technique is to clear each status bit separately by writing its mask to the register as the corresponding interrupt service is performed. note: wholesale clearing of all status bits by writing ffh to the register is not recommended, since this may clear status which has just been set and not yet read by the system. table 5. dlcr1 e receive status register bit symbol type description 7 rx pkt r c 0 receive packet: set when a new receive packet is stored in the receive buffer. can generate interrupt if enabled by dlcr3<7>. 6 bus rd err r c 0 bus read error: set when a ready response cannot be issued within 2.4 m s after the rd signal is asserted. occurs when reading an empty buffer. can generate interrupt if enabled by dlcr3<6>. 5 dma eop r c 0 dma end of process: set when the host dma asserts the eop pin indicating that the process is finished. when set, inhibits further assertion of dreq. cleared by writing 00h to bmpr12. do not clear by writing 1 to this bit as this may result in unwanted dreq . can generate interrupt if enabled by dlcr3<5>. 4 rmt 0900h r c 0 remote control packet received: this bit is set if a packet is received with 0900h in its length/type field (two bytes following the source address, received msb first). can generate interrupt if enabled by dlcr3<4>. 3 short err r c 0 short packet error: set when a packet is received with less than 60 bytes, excluding its preamble and crc fields. such a packet usually indicates a collision has truncated its original length, since ieee 802.3 minimum length is 60 bytes. can generate interrupt if enabled by dlcr3<3>. see also table 8. 2 align err r c 0 alignment packet error: this bit will assert if a packet is received with an alignment error, meaning there were 1 to 7 extra bits at the end of the packet. such an occurrence usually indicates a collision, or a faulty transceiver. can generate interrupt if enabled by dlcr3<2>. see also table 8. 1 crc err r c 0 crc packet error: this bit is set if a packet is received with a crc error. this usually indicates a collision has corrupted the packet. can generate interrupt if enabled by dlcr3<1>. see also table 8. 0 rx buf ovrflo r c 0 receive buffer overflow: this bit will be set if the receive buffer becomes full and must reject a packet for lack of space. can generate interrupt if enabled by dlcr3<0>. does not get set in loopback mode.
mb86960 transmit interrupt enable register this register contains the bits which enable or mask the status bits in dlcr0 from generating interrupts. only bits 7, 2 and 1 can generate interrupts. the other bits are not used. see table 6. table 6. dlcr2 e transmit interrupt enable register bit symbol type description 7 int en r w 0 interrupt enable: when high, enables tx done to generate interrupt. see also dlcr0<7>. 6 0 n 0 reserved: write 0. 5 int en n 0 reserved: write 0. 4 0 n 0 reserved: write 0. 3 0 n 0 reserved: write 0. 2 int en r w 0 interrupt enable: when high, enables col to generate interrupt. see also dlcr0<2>. 1 int en r w 0 interrupt enable: when high, enables 16 col to generate interrupt. see also dlcr0<1>. 0 0 n 0 reserved: write 0.
mb86960 receive interrupt enable register this register provides control for enabling or masking interrupts based on the assertion of status bits in dclr1, the receive status register. see table 7. transmit mode register this register contains two control bits associated with transmission, a general-purpose control bit which drives a pin on the chip, and a collision counter. see table 9. table 7. dlcr3 e receive interrupt enable register bit symbol type description 7 int en r w 0 interrupt enable: when high, enables rx pkt to generate interrupt. see also dlcr1<7>. 6 int en r w 0 interrupt enable: when high, enables bus rd err to generate interrupt. see also dlcr1<6>. 5 int en r w 0 interrupt enable: when high, enables dma eop to generate interrupt. see also dlcr1<5>. 4 int en r w 0 interrupt enable: when high, enables rmt 0900h to generate interrupt. see also dlcr1<4>. 3 int en r w 0 interrupt enable: when high, enables short err to generate interrupt. see also dlcr1<3> and table 8. 2 int en r w 0 interrupt enable: when high, enables align err to generate interrupt. see also dlcr1<2> and table 8. 1 int en r w 0 interrupt enable: when high, enables crc err to generate interrupt. see also dlcr1<1> and table 8. 0 int en r w 0 interrupt enable: when high, enables rbuf ovrflo to generate interrupt. see also dlcr1<0>. table 8. network error monitoring modes acpt bad pkts dlcr5<5> acpt short pkts dlcr5<3> int en short errors dlcr3<3> int en align errors dlcr3<2> int en crc errors dlcr3<1> mode description 0 0 0 0 0 normal non-monitor mode. 0 0 1/0 1/0 1/0 error interrupts only, if enabled. 0 1 0 1/0 1/0 save short packets if otherwise error free in buffer; interrupts only for alignment and crc errors, if enabled. rx pkt will be set high if short packet received. 1 0 0 0 0 save packets with short, alignment and/or crc errors in buffer; rx pkt will be set high if packet with error received. all others do not use. note: packet acceptance requires both error filter acceptance and address filter acceptance.
mb86960 table 9. dlcr4 e transmit mode register bit symbol type description 7 col ctr 3 r 1 collision count 3: dlcr4<7:4> plus 1 indicates the number of consecutive collisions encountered by the current transmit packet. (read only). see table 10. 6 col ctr 2 r 1 collision count 2: dlcr4<7:4> plus 1 indicates the number of consecutive collisions encountered by the current transmit packet. (read only). see table 10. 5 col ctr 1 r 1 collision count 1: dlcr4<7:4> plus 1 indicates the number of consecutive collisions encountered by the current transmit packet. (read only). see table 10. 4 col ctr 0 r 1 collision count 0: dlcr4<7:4> plus 1 indicates the number of consecutive collisions encountered by the current transmit packet. (read only). see table 10 3 0 n 0 reversed: write 0. 2 cntrl r w 1 control output: the inverse of this is bit is output for general use on pin 95. 1 lbc r w 1 loopback control: this bit controls the loopback function of the nice encoder/decoder. a 0 in this bit places the chip in internal loopback mode. 0 en tx defer r w 0 enable transmit defer: program this bit low for normal network operation. when high, the transmitter will not defer to traffic on the network. table 10. collision count collision count 16 col dlcr0<1> dlcr4<7> dlcr4<6> dlcr4<5> dlcr4<4> col dlcr0<2> 0 0 0 0 0 0 0 1 0 0 0 0 1 1 2 0 0 0 1 0 1 3 0 0 0 1 1 1 . . . . . . . . . . . . . . . . . . . . . 15 0 1 1 1 1 1 16 1 0 0 0 0 1 receive mode register this register contains six bits which control receiver function, and one receive buffer status bit. see table 11. the status bit, rx buf empty (receive buffer empty), is very important to the software routine which reads receive packets from the buffer. it tells the host routine whether there are any packets in the receive buffer which are complete and ready to read. in a multi-tasking system, this indicator would be used in conjunction with an interrupt when rx pkt asserts, which means a packet has arrived in memory. the interrupt would be used to start the routine which reads packets from the buffer. as this routine begins, the interrupt on rx pkt can be disabled to prevent unneeded interrupts. after the first packet is read from the buffer, the rx buf empty bit would be read to see if any more packets have come in (packets may, at times, arrive in bursts). if the buffer is not empty, another packet would be read out, and this procedure repeated until the buffer is empty. after emptying the buffer, the host clears rx pkt, then re-enables interrupts on rx pkt, checks the buffer status one more time (since a packet can come in at any time), then exits to do other tasks.
mb86960 two of the control bits allow reception of packets with certain types of errors. the acpt bad pkts bit, when set, causes the receiver to retain and store in the buffer packets with crc, alignment and/or short length errors provided there was no indication of collision during reception. likewise, the acpt short pkts bit, when set, allows the retention of short packets down to and including only six bytes in length, excluding preamble and crc, provided there was no indication of collision during reception and no alignment or crc error. under normal operation, packets with less than 60 bytes, the ieee 802.3 lower limit, would be discarded. these functions are provided for diagnostic purposes. packets are accepted only if both the address filter and the error filter are passed. packets with no content errors, i.e., short, alignment or crc, are accepted without regard to collision indicators. table 11. dlcr5 e receive mode register bit symbol type description 7 0 n 0 reserved: write 0. 6 rx buf emty r 1 receive buffer empty: status bit which indicates that the receive buffer does not have any complete packets to read. (read only). 5 acpt bad pkts r w 0 accept packets with errors: when set high, allows packets with crc, alignment and/or short length errors to be saved into the receive buffer for analysis, provided there was no indication of collision during reception. otherwise such packets would be discarded automatically by the receiver and removed from the buffer. see also table 8. 4 40 bit addr r w 0 40 bit address: when set high, instead of the customary 48-bit node id address filter, only the first 40 bits of the node id are compared (node id 04). 3 acpt short pkts r w 0 accept short packets: when set high, allows short packets (packets with less than 60 bytes, excluding preamble and crc, i.e. below ieee minimum length) down to 6 bytes, excluding preamble and crc, to be saved into the receive buffer, provided there was no crc or alignment error and no indication of collision during reception. otherwise such packets would be discarded automatically by the receiver and removed from the buffer. see also table 8. 2 1 n 0 reserved: write 1. 1 af1 r w 0 address filter mode: af1 and af0, dlcr5<1:0>, control the address filtering on incoming packets. see table below under af0. 0 af0 r w 1 address filter mode: af1 and af0, dlcr5<1:0>, control the address filtering on incoming packets: af1 af0 description of address accepted 0 1 node id, broadcast, multicast & 2nd-24th bits of node id 1 0 node id, broadcast, multicast & hash table 0 0 reject all packets 1 1 accept all packet note: self reception of broadcast and multicast packets prohibited except in aaccept all packetso mode. when lbc is low (loopback mode) broadcast packets can be self-received, except in areject all packetso mode.
mb86960 configuration registers 0 and 1 basic system configuration bits are found in these two registers. among the configuration controls found here are physical packet buffer memory size, partitioning between transmit and receive buffers, widths of memory and system buses, byte lane control, chip configuration and power down control. most of these configuration parameters will be programmed only during initialization after power start and hardware reset. see tables 12 and 13. table 12. dlcr6 e configuration register 0 bit symbol type description 7 dlc en r w 1 enable data link controller: when low, enables the receiver and transmitter sections of the nice chip. this bit must be set high during initialization and later set low to enable loopback testing and operation of the network. program node id only when this bit is high. 6 1 n 0 reserved: write 1. 5 sb/sw r w 1 system byte/word bus width: when high, system bus will operate in 8-bit data mode; when low, 16-bit data mode is selected. see also bb/bw below. 4 bb/bw r w 1 buffer byte/work width: when high, buffer memory will operate in 8-bit data mode; when low, 16-bit data mode is selected. see table for allowable combinations with sb/sw: sb/sw bb/bw system buffer 0 0 word word 0 1 word byte 1 0 do not use 1 1 byte byte 3, 2 tbs 1, 0 r w 01 transmit buffer size: selects size of transmit buffer(s). see table: 00 1 2kb 2kb 01 2 2kb 4kb 10 2 4kb 8kb 11 2 8kb 16kb tbs no. tx size each total size 1,0 bufs tx buf tx buf 1, 0 bs1, 0 r w 10 buffer size: selects physical size of total sram buffer memory for both transmit and receive functions. see table: bs1 bs0 sram size 0 0 8kb 0 1 16kb 1 0 32kb 1 1 64kb
mb86960 table 13. dlcr7 e configuration register 1 bit symbol type description 7, 6 e/d cnf 1,0 r w 00 encoder/decoder configuration: selects the operating mode of the controller-encoder/decoder functions and their interface. see table below and pin descriptions for the monitor pins, txd, tck, ten, lbc, rxd, rck, crs and col : e/d cnf 1 e/d cnf 0 registers 00 normal nice: internal encoder/decoder active. monitor pins inactive. 01 nice + monitor: internal encoder/decoder active. monitor pins outputting all controller/encoder/ decoder interface signals 10 encoder/decoder bypass: internal encoder/ decoder not used. monitor pins can be used to interface controller to external encoder/decoder. 11 encoder/decoder test: controller inactive, encoder/decoder active. monitor pins used to test encoder/decoder. 5 pwrdn r w 1 power down: when set high, enables power to the chip for all functions; when set low, places chip in power down mode for power conservation. 4 rdypol r 0/1 ready pin polarity: reads the state of the rdy pol pin 94. 3, 2 rbs 1, 0 r w 00 register bank select: provides the indirect address for selection of one of the three sets of registers to access when the physical register address is xxx8hxxxfh. the lower 7 registers are not bank-selectable. see table: rbs1 rbs0 registers 0 0 dlcr0-7, dlcr8-f 0 1 dlcr0-7, ht8-f 1 0 dlcr0-7, bmr8-f 1 1 reserved 1 eoppol r w 0 eop pin signal polarity: when high, the eop pin is active-high; when low, eop is active-low. 0 m..l/ l..m r w 0 byte order control: selects byte lane ordering for packet data in the buffer (applies only in system word mode). in both most..least and least..most modes, the first and second bytes of the packet will appear in the same word on the system bus. when this bit is high (m..l mode), the first and all odd-numbered bytes of a packet and its header will appear on the high byte of the system bus. note that header bytes are also swapped.
mb86960 note to software engineers regarding nice/ether- star ? compatibility: if you desire to use the same node driver for fujitsu's nice and etherstar controllers, the driver can determine which chip is being used by reading dlcr7 and/or dlcr6 after hardware reset. nice will read 30b6h or 20bgh (30 or 20 for dlcr7 and b6 for dlcr6); etherstar will read 0000h. power-down mode saves power when the device is not in use. when ready to place the nice chip in power down mode, first write 1 to dlcr6<7>, dlc en , to turn the receiver and transmitter off, then write 0 to dlcr7<5>, pwrdn . to exit the power-down mode, write 1 to pwrdn . register contents will be preserved, unless a hardware reset is issued. hardware reset will also terminate the power-down mode. byte order control provided by the most..least/ least..most bit, dlcr7<0>, provides compatibility with various higher-level protocols, such as tcp/ip and xns. these protocols may have different transmission order of the bytes within a word. when m..l/l..m is low, the least significant byte of the word is transmitted first, followed by the most significant. when m..l/l..m is set high, the byte order is reversed. this feature applies only when the system bus is operated in 16-bit (word) mode. the byte order control works by reversing or not reversing the bytes of all words as they pass between the buffer memory and the system bus. thus all data stored in the transmit buffer or retrieved from the receive buffer is affected, including the nontransmitted headers. the nice registers, other than the buffer memory port, bmpr8:9, are not affected by this control bit. care must be taken in the software driver code to reverse the header information as well as the packet data when using this feature. examples follow. example of using least..most byte ordering: system bus transmit packet: high byte low byte tx length, high byte tx length, low byte destination addr, 2nd byte destination addr, 1st byte source addr, 2nd byte source addr, 1st byte length field, low byte* length field, high byte* data field, 2nd byte data field, 1st byte receive packet: high byte low byte unused; reserved receive packet status rx length, high byte rx length, low byte destination addr, 2nd byte destination addr, 1st byte source addr, 2nd byte source addr, 1st byte length field, low byte* length field, high byte* data field, 2nd byte data field, 1st byte example of using most..least byte ordering: system bus transmit packet: high byte low byte tx length, low byte * tx length, high byte* destination addr, 1st byte destination addr, 2nd byte source addr, 1st byte source addr, 2nd byte length field, high byte length field, low byte data field, 1st byte data field, 2nd byte receive packet: high byte low byte receive packet status unused; reserved rx length, low byte * rx length, high byte* destination addr, 1st byte destination addr, 2nd byte source addr, 1st byte source addr, 2nd byte length field, high byte length field, low byte data field, 1st byte data field, 2nd byte note: asterisk indicates numerically reversed byte ordering.
mb86960 node id registers the node id registers are accessed in register bank a0o at register addresses xxx8hxxxdh. during initialization of the node, the unique ethernet address assigned to the node is loaded into these registers. the first register at xxx8h corresponds to the first byte of the node id, which corresponds to the first address byte to be received as a packet arrives from the network. if the chip is configured to do so in its address filter mode bits, dlcr5<1:0>, the destination address field of an incoming packet will be compared to the node id stored in these registers. if there is a match, provided the packet passes the error filter, it will be accepted. these registers are readable as well as writable, but they should not be accessed while the receiver is enabled. to avoid interaction with the receiver, access these registers only when dlc en is 1. it is recommended that they be written and read only during initialization before enabling the receiver, i.e. before writing 0 to dlc en , dlcr6<7>. the address contained in these registers is used only for receive (destination) address filtering, not for the source address of outgoing packets. outgoing packet addresses must be provided by the system as part of the packet data. within each byte, the bits are transmitted and received on the network least-significant bit first. see table 3 for the transmission bit order, which follows the bit numbering in this table. time domain reflectometry (tdr) counter the tdr counter can be used to get a rough indication of the location of a fault on the network, if one exists. when a node transmits, a short or open on the network would cause a reflected signal to the node's receiver which can sometimes be detected. the reflection will cause the carrier sense to fail and/or a false collision to be detected. this affect, time domain reflectometry, can be used to estimate the distance along the network cable from the node to the fault. the tdr counter counts the number of bits transmitted before either a collision occurs, or carrier sense is lost, whichever comes first. if neither occur during transmission of the packet, the count is cleared. the amount of elapsed time this represents is two (2) times the signal delay from the node to the fault. an open on the network will usually cause a false collision, whereas a short is more likely to cause loss of carrier sense. the tdr count comes from dlcr14 and 15. dlcr14 is the least-significant byte, dlcr15 the most-signifi- cant. only the lower 14 bits of the counter are equipped, which is more than is needed for an ieee or ethernet lan. (the top two bits, dlcr15<7:6>, are always 0.) to perform the tdr test for a fault, first enable interrupts for transmitter done (tx done). this is done by setting dlcr2<7> high. (an alternative to using the interrupt would be polling the tx done bit looking for a high level.) set the 16 collisions register, bmpr11, to 07h for this test (no halt, skip failed packet). clear all status bits by writing ff86h to the receive and transmit status registers. next, transmit, or attempt to transmit, a packet of 600 bits or more in length. up to 16 attempts may be made automatically if collisions are being indicated. upon completion of the transmission attempt(s) tx done will go high, generating an interrupt if enabled. when this occurs, read the transmit status register and the tdr register. interpreting the results: if the count is zero, no fault was detected. if the count is greater than zero but smaller than the packet length, it may indicate a cable fault. if the count is less than 525, there may have been a real collision occurring during the test. real collisions normally occur within the first 65 bytes of the packet, including preamble. take note of the error messages, col and cr lost. col high suggests a cable open, whereas cr lost suggests a short. it is best to repeat the measurement several times, then throw out the anomalous values, if any, and average the rest. a cluster of readings at about the same value is a strong indicator of a valid fault measurement. if such a cluster of readings occurs, multiply the average of the cluster by 39 feet to estimate the distance from the node to the fault. (39 ft. = (100 ns x .8 x 186,282 mi/s x 5280 ft/mi)/2 ... this assumes the network is mostly coaxial cable with signal propagation speed of approximately .8 x c, the speed of light.)
mb86960 hash table the hash table provides a means for filtering incoming multicast packets so that the host processor does not have to process ones that are not of interest. the principle employed in this filtering scheme was originally developed by computer science to arrange a large number of elements of an array or database in such a way that facilitates searching for elements associated with a given key or datum. the `hash function' is a mathematical or logical function which maps all possible elements in a domain onto a smaller domain called the `hash table'. as an example, suppose the following hashing function is used: atreating the multicast address as a non-negative 48-bit integer, divide this number by 64 and take the remainder.o this function will map all multicast addresses into a 64-element hash table since the remainder can be only the integer values 0 through 63. applying this hashing function results in taking the least-significant 6 bits of the multicast address as an integer. in the hash table, for each element, 0 through 63, a single bit is stored which indicates whether the address is to be accepted (1) or rejected (0). if, for example, the node belongs to three multicast groups, only three or fewer of the hash table elements will store 1's, the rest 0's. the scheme allows the acceptance of any number of the addresses, including all of them. the limitation is that there may be addresses not of interest used on the network which also fall into the `accept' elements, so in this case the filtering is imperfect. but in any case, most of the nonapplying addresses can be filtered out in this way. the actual hashing function used in the nice chip is this: acalculate the crc on the multicast address and take the high-order 6 bits of this calculationo. the six bits are used to address the elements of the hash table. if a 1 is stored in an element of the table, associated packets are accepted. the hash filter criterium is only used on multicast addresses, which all start with a 1. node id's, which start with a 0, are not filtered by the hash filter. the broadcast address, a special case of the multicast set wherein all the bits are 1's, will be accepted anyway unless the areject all packetso mode is selected. figure 12 shows the register core, a modified shift-right register, used in generating and checking crc's. whereas some controllers share a single such core between transmitter and receiver, nice has two of these, one for the generator and one for the checker, allowing both to operate concurrently for self-receive. to begin the calculation, the register is first set to all 1's. for the generator case, as the packet is transmitted, the data is clocked serially into the left-hand end of the register starting with the 48 bits of the destination address (the preamble is skipped). after the last bit of the `data' field is clocked into the register, the crc calculation is finished. the feedback line is then forced low and the register becomes a simple shift-right register. its contents are then shifted out serially and transmitted, appending the crc to the end of the packet. for the crc checker, the calculation starts out the same way as for crc generation feeding the incoming data into the register. but in this case, the crc field of the packet is also fed into the calculation. the result is a fixed constant in the register if no crc error has occurred. for the hash filter, after the last bit of the destination address has been clocked into the register, the left-hand six register bits are stored in another register used to address the hash table elements. the left-most bit is most significant. the left-most three bits are used as the hash table register address and the right-most three as the bit address within a register byte. having selected a hash table element in this way, a 1 in the table will indicate the packet is to be accepted, provided it is a multicast packet (first bit of destination address must be 1), and passes the error filters. the hash filter is only employed when the address filter mode select bits, af1, af0 are 0, 1, selecting the anode id, broadcast, multicast + hash tableo mode. like the node id registers, the hash table registers should only be accessed when the receiver is disabled, i.e. when dlc en is high, to avoid interaction with the receiver. there are eight bytes of registers in the hash table containing the 64 1-bit elements (refer to table 1 for location). source code software examples showing how to calculate entries for the hash table are available from fujitsu microelectronics, semiconductor division, in c and assembly language.
mb86960 = exclusive or figure 10. crc register core + + + + + + + + + + + + + d q d q d q + dat a d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q d q q d q d q d q d q d q d q d q
mb86960 transmit and receive packet headers both transmit and receive packets have headers stored with them in the buffer memory which are not part of the transmitted packet. these headers precede the packet data. transmit packet length an 11-bit integer indicating the number of bytes in the packet to be transmitted, excluding preamble and crc fields which are generated by the nice chip. see table 3 for bit locations, and description for dlcr7<0>, m..l/l..m. receive packet status the receive packet header consists of one byte of packet status, an unused byte and two bytes (11 bits) for packet length in bytes. see table 3 for location of the bits, and description for dlcr7<0>, m..l/l..m. bits 1, 2, 3 and 4 of the status byte are an image of the same bits in the receive status register, dlcr1, with respect to the packet that follows. bit 5 is the good pkt bit. a 1 in this bit location indicates no errors were detected in the packet. bits 0, 6 and 7 are unused and are always 0. receive packet length the third and fourth bytes of the receive packet header indicate the total number of bytes in the stored packet data. see table 3 for location of the bits, and description for dlcr7<0>, m..l/l..m. buffer memory port registers the buffer memory port registers, bmpr815, provide the host access to the buffer memory and certain control functions. it is recommended that this bank be selected most of the time the chip is on the network for convenience in accessing the buffer memory and the control bits (register bank select = 11 binary). refer to table 1 for location of these registers. writing a byte/word to bmpr8, the buffer port, transfers that data to the currently addressed location in the transmit buffer and increments the transmit buffer pointer to point to the next byte/word. reading a byte/word from this port transfers the contents of the currently-addressed location in the receive buffer to the host and increments the receive buffer pointer to point to the next byte/word. bmpr9 is used only in word mode as the high byte of the word. in word mode, all transfers must be 16-bits wide, as the buffer port does not support byte-wide transfers in this mode. all other registers can be accessed word-wide, high byte only or low byte only as desired. table 14. bmpr10 e transmit start register bit symbol type description 7 tx start w 0 transmitter start: writing 1 to this bit commands transmitter to start transmitting the packet(s) loaded into the transmit buffer. before doing so, the transmitter must be idle (not busy with another buffer). the tx done bit is used to determine the required transmitter status, idle or busy. 60 tx pkt cnt r w 0 transmit packet count: a binary integer written by the system to indicate the number of packets contained in the transmit buffer for transmission. this information can be loaded at the same time the tx start bit is set high. as the transmitter finishes transmitting each packet, this counter is decremented. the value can be read by the system to see how many packets remain to be transmitted.
mb86960 transmit start register the transmit start register, bmpr10, contains the tx start bit and the tx pkt cnt. writing 1 to the tx start bit immediately starts the transmitter. the transmit packet count is a 7-bit binary integer written by the host to indicate the number of packets in the transmit buffer to be transmitted. see table 14. this register should only be written when the transmitter is idle. it can be read at any time. tx start will always read as 1. 16 collisions control register this is a command register to control the actions taken when 16 consecutive attempts to transmit a packet are all met with collision. table 15 summarizes the use of this register. it serves as both a mode setup register and an action command register. as a mode select register, two functions are selectable. firstly, automatic continuation or halt after 16 collisions can be selected. if automatic continuation is selected, there is an option to continue attempting to transmit the same packet, or skip to the next packet. if halt is enabled, the transmitter is restarted after a halt by writing any action code listed in table 15 to this register. dma enable register this is a write-only register which is used to enable and clear either receive read dma or transmit write dma. refer to table 14 for the codes. dma burst register (bmpr13) this register is used to select the burst length for dma operation. the burst length can be 1, 4, 8 or 12 transfers. each transfer is one byte or one word, depending on the mode selected, system byte or system word (see sb/sw in dlcr6). code no. of transfers 00h 1 01h 4 02h 8 03h 12 table 15. 16 collision action codes (written to bmpr11) action code description 02h or 03h mode setup: halt after 16 collisions. 02h command: resume transmitting, repeat failed packet (for use following a halt). terminates the halt. instructs transmitter to resume transmitting by repeating the failed packet. the collision counter is reset, allowing up to 16 additional attempts to be made. halt after 16 collisions. 03h command: resume transmitting, skip failed packet (for use following a halt). terminates the halt. instructs transmitter to skip the failed packet and resume transmitting with the next packet in the buffer. the collision counter is reset, allowing up to 16 additional attempts to be made. if there is no next packet, the transmitter will deactivate, setting tx done as it does so. halt after 16 collisions. 06h mode setup: continue automatically after 16 collisions, repeat failed packet. warning: if the network medium is disconnected, transmission attempts will usually result in false collision detection. under this condition, this mode will cause the transmitter to continue re-attempting transmission of the same packet indefinitely. interrupt or periodic polling of the status bits should be used to detect this condition. 07h mode setup: continue automatically after 16 collisions, skip failed packet. warning: this mode will result in failure to transmit some packets, since it skips a packet which has had 16 collisions. this condition is rare on a healthy network, but it does happen. to avoid this, use mode 06h. table 16. dma enable register (bmpr12) action code description 01h enables transmit write dma 02h enables receive read dma 00h clear or terminate dma activity, dma eop status bit and associated interrupt, if any. normally used as response to end of process (dma eop) interrupt.
mb86960 skip packet register (bmpr14) only one bit in this register is active, bit 2, the rest are 0. writing 04h to this register commands the buffer controller to skip the balance of the current receive packet in memory. the bit can then be read to see when the skip process is complete (within 300 ns). the bit returns to 0 when the chip is ready to read the next packet, if there is another packet, or stop reading if there is not. limitation of use: do not use this feature before reading at least four (4) times from the beginning of the packet, nor if there are only eight (8) or fewer bytes left of the packet in the buffer. doing so may corrupt the receive buffer pointers. bmpr15 is unused and reserved for possible future use. write only 0's to this register. transmitter circuits circuits within the transmitter include a transmitter state machine, a small fifo for pipe-lining the packet data, preamble generator, crc generator, parallel to serial converter, backoff generator, inter-packet gap timer and a time domain reflectometer (tdr) counter. the transmitter state machine provides sequencing of events for the transmitter, including idle, preamble, data, crc, inter-packet gap, jam and backoff. it detects various transmit error conditions and sets appropriate bits within the dlcr registers. the pipeline fifo provides elastic buffering that the buffer controller can load with data to be transmitted. nice's crc generator calculates the ethernet 32-bit crc on the destination and source address, the length field and the data field as specified by the iso/ansi/ ieee 8802-3 specification for ethernet. this value is appended to the end of the packet. transmit error processing nice has four transmit error status bits in its transmit status register (dlcr0) for reporting the three possible transmit errors. the errors are: 1) loss of carrier during transmission, which usually indicates a medium fault or a collision, 2) collision, and 3) 16 consecutive collisions. the latter two can be enabled separately to generate interrupts. if nice detects a collision during transmission, it will automatically try to retransmit the packet until sixteen at- tempts have been made. collision counter dlcr4<7:4>, automatically increments after each collision up to the sixteenth collision, at which time it rolls over to zero. (bit 7 is the most-significant of the four bits.) appropriate status bits in the transmit status register and transmit mode register are set in case of a collision-terminating transmission. another status bit (16 col) indicates that sixteen consecutive attempts to transmit a packet have been made and all have been terminated by collision. this case may indicate a network problem. for example, a disconnected cable or terminator will produce false collisions. but 16 collisions can occur normally, although rarely. a pseudo-random number generator provides the collision backoff function. this is clocked at the bit rate, 10 mhz, so that distances between stations become part of the randomizing function. it is sampled at the time of collision, masking all but the appropriate number of bits specified by the 88023 backoff algorithm. this value is then counted down at the slot-time rate (512 bits) to generate the backoff interval. for a first collision, only one bit is used, giving a backoff of either 51.2 microseconds or 0. for a second consecutive collision, two bits are used, and so forth, up to ten bits. from the tenth to the 16th collision, 10 bits are used. this gives a pseudo-random backoff interval of from 0 to 52.38 ms, the so-called `binary exponential backoff' for collisions per 8802-3. time domain reflectometry the tdr function provided counts the actual number of bits transmitted for each packet before an indication of either collision or carrier loss occurs, or the transmission completes. if a transmission completes without error indications, the tdr counter is cleared. see also the register description for dlcr14 and dlcr15. media access control nice's transmitter state machine implements the media access protocol for 8802-3 networks called csma/cd, carrier sense, multiple access with collision detection. the `carrier sense' part means that the controller monitors the network for carrier from other nodes, and defers transmission while other nodes are transmitting (collision avoidance). but collisions can still occur when two nodes, perhaps separated on the network by several microseconds, start to transmit at nearly the same time. this is handled by the `collision detection' part. all nodes are required to monitor the network for collisions and, when involved in one, transmit a 32-bit `jam' to reinforce the collision, then terminate transmission. later, after waiting a pseudo-random backoff interval, the node automatically re-attempts to transmit the packet. between packets, there must be a gap of at least 9.6 microseconds during which time the trunk cabling is idle. nice's transmitter state machine measures this interval starting from the end of a packet on the network. it will not transmit until this interval has expired. during the
mb86960 first 2/3 of the interval, if for some reason carrier reappears on the network, nice resets its interval timer to re-time the interval from the end of the new transmission. such an event can occur during a collision, since data and carrier indications can be corrupted by the superimposition of the two packets. during the last 1/3 of the interval, nice will ignore a carrier indication if it occurs. this is in accordance with 88023, intended to assure fairness and equality in access to the network. if one station starts to transmit slightly ahead of another, no advantage will be gained by the slightly earlier start. both nodes will transmit, a collision will occur, and the media-access contention will be resolved by backoff interval differentials. data encoder nice serializes the data for transmission, and converts each bit to manchester code, the format used on the network media. manchester code for `1' is a 100 ns interval starting with a low, ending with a high, with a low-to-high transition at the 50 ns point. manchester code for `0' is the inverse of this. see figure 14 for a block diagram of the encoder/decoder section. operating with an external encoder/decoder an option is provided on nice to disable the on-chip encoder/decoder circuits and use an external encoder/de- coder. specific details are given in the register description section in table 13, configuration register 1 (see dlcr7<7:6>). transmit packet processing to transmit one or more packets, the host system first loads the packet(s), preceded by a 2-byte header giving their lengths, into a transmit buffer by writing the data to the buffer memory port register, bmpr<8:9>. only the destination address, source address, length field and data field of the packets are loaded by the system, nice generates the rest. when the packets are loaded, the system turns the transmitter on to initiate transmission. this enables nice to transmit. observing the media access protocol, nice defers transmitting to carrier from other nodes, minimum inter-packet gap intervals and backoff intervals if any, then begins to transmit. nice serializes the data and encodes it in manchester code. it generates the preamble field at the beginning, and calculates and appends the crc field at the end, followed by the end-of-packet delimiter, which is a non-man- chester code. the manchester-encoded signals are output through a differential driver to the tx data pins to the external transceiver. the driver is capable of driving a 50-meter segment of 78-ohm transceiver cable, as specified in the 88023 standard. 270-ohm resistors to gnd are required externally to pull down txdata+ and txdata. see figures 11 and 12 for suggested cable interfacing. the host system activates the transmitter by writing 1 to the tx start bit and the packet count to tx pkt cnt. after this is done, the transmitter will transmit each packet in the buffer in the order that they were loaded. if a collision occurs, the transmitter automatically retransmits the packet until successful, or until 16 consecutive attempts have ended in collision. in the latter case, depending on the mode selection made at initialization time, the transmitter will either 1) continue to try to transmit the same packet, starting again with a collision count of zero, 2) skip the current packet and try to transmit the next packet, starting with a collision count of zero, or 3) halt and wait for instruction from the host. in the third case the host can select to either 1) terminate by setting dlc en high, 2) continue to attempt to transmit the same packet (collision counter gets reset) or 3) skip the current packet and try to transmit the next packet (collision count = 0). col+ col rxdata+ rxdata txdata+ txdata nice 39w 39 270w 270w note: transformers are 1:1 and 27 h minimum. a. ieee 802.3 aui (transceiver) cable termination 39w 39w figure 11. transceiver interface termination tranceiver (aui) cable 0.1 f 0.1 f
mb86960 1550 1550 1550 1550 figure 12. transceiver interface termination b. simplified termination for coaxial transceiver col+ col rxdata+ rxdata txdata+ txdata nice on-board mbl8392a coaxial trans ceiver 240w 240w 78w 270w 270w c. simplified termination for on-board 10base-t transceiver col+ col rxdata+ rxdata txdata+ txdata nice on-board mb86962 10base-t trans ceiver 78w 270w 270w 78w 78w 0.1 f 0.1 f 0.1 f 0.1 f 0.1 f 0.1 f 0.1 f 0.1 f 0.1 f 0.1 f 0.1 f 0.1 f collision signal processing as collisions are detected on the network media, the external transceiver generates a 10 mhz signal on the col differential inputs to the nice's encoder/decoder section. when this signal is detected by nice, it asserts the internal collision line, and in some modes the col pin, pin 92, is also asserted. the col differential driver inputs require termination like that for the rxdata inputs. see figures 11 and 12 for suggested cable termination. loopback loopback capability is provided to allow testing of nice without sending signals onto the lan media. the loopback function is invoked by clearing the lbc bit, dlcr4<1>. loopback operation is illustrated in figure 13. data is routed from the transmit buffer through a fifo to the transmit section of the data link controller, through the internal manchester encoder, back through the manchester decoder, through the receiver section of the data link controller, and is then stored in a receive buffer. the test software can then read and check the received packet which has traveled through nearly all transmit and receive sections of the chip. when an external encoder/decoder is used, the data is output on txd and received at rxd. the external manchester encoder/decoder should respond to assertion of its lbc input by looping its transmitter output to its receiver input internally, and should block the transmit data from appearing at its network output pin. fujitsu's mb86951 and mb502a encoder/decoders, and mb86961 encoder/decoder with 10base-t transceiv- er, for example, all respond in this way. figure 13. nice in loopback mode nice internal encoder/decod er no signals appear at output pins nice data link controller section txd * rx d* lbc * * in aniceo mode, these are internal signals and no signals appear on the corresponding pins.
mb86960 receiver circuits the receiver includes a receive state machine, serial to parallel conversion, pipe-line fifo, preamble recogni- tion, bit and byte framing, address filtering, crc and other error checking and `end-of-packet' symbol recognition. the receiver state machine provides sequencing of events for the receiver, including idle, busy, address filtering, data storage, etc. it detects various receive error conditions and sets appropriate bits within the dlc registers. a small data fifo provides elastic buffering for synchronization with the buffer controller timing, and buffering data while the buffer controller is servicing other buffer memory access requests. all received bytes are delayed by four bytes before storing in the receive buffer so that the last four bytes of the packet can be stripped and checked for correct crc. (the crc bytes are not transferred to the receive buffer.) during reception, packets are automatically rejected if space in the receive buffer is insufficient to hold the entire received packet. status bits in the receive status register are set to indicate this and other errors. the receive errors are: 1) bus read error, which occurs if the host system attempts to read from an empty receive buffer (this need never occur if the rx buf empty bit is checked), 2) short packet error, 3) alignment error (incomplete byte fragment at end of packet), 4) crc error and 5) buffer overflow. there is one additional possible receive error which the chip leaves to the software to check -- length error. when the length of the packet does not match the value in the length field of an 88023 packet, this is a length error. some protocols use the length field for other purposes, for example, the dix protocol uses it for a packet type code. in this case, allowed type codes do not overlap allowed packet length values, providing a means to distinguish which protocol is being used (if length value >1500, it's dix type code). length check can be made conditional on protocol type if necessary to support other protocols like dix. figure 14. encoder/decoder block diagram collision signal decoder collision signal receiver col interface to encoder/decoder aui interface col+ rxdata+ rxdata+ pll decoder rx line receiver col rck rxd lookback crystal oscillator x2 x1 manchester encoder tx line driver txdata txdata+ ten txd lbc tck crs
mb86960 decoder functions the data decoder section performs three functions on the data received at the differential receive inputs (rxda- ta ) from the transceiver: clock recovery, carrier detection and manchester data decoding. clock recovery and data separation are accomplished by the use of a phase locked loop. use of proprietary techniques in the pll allows lock-on to be accomplished within 67 bit times of the beginning of the preamble, and permits stable operation with input signal jitter of up to 18 ns. carrier detection is indicated to the controller by assertion of the crs signal, which occurs shortly after a signal appears at rxdata . the recovered clock is supplied to the controller on rck, and is also used to convert the manchester encoded data to nrz format. nrz data is output on rxd. transitions in the state of rxd are synchronous with the falling edge of rck. during idle periods, rck is a free-running 10 mhz clock. the rxdata differential inputs are usually terminated with two 39-ohm resistors in series and an 0.1 f bypass capacitor to ground at their junction, as shown in figure 11. monitoring the network whenever the data link section is enabled (dlc en = 0), the receiver is constantly monitoring the network for carrier. signals which exceed the ac and dc squelch thresholds of the rxdata input section cause the internal carrier sense (crs) line to assert, which in turn causes the receiver to attempt to receive a packet. refer to figure 2 for a block diagram of the encoder/decoder section. (the carrier sense function is also used by the transmitter to defer to transmissions from other nodes, except when dlcr4<0> is high.) after the pll decoder acquires bit-synchronization with the incoming signal, the receiver monitors the data stream for the end-of-preamble bit pattern, two consecutive 1's ending the preamble's pattern of alternating 1's and 0's. this pattern gives the receiver byte and field synchronization, because the bit immediately following the two 1's is the first bit of the first byte of the packet's destination address field. when packet transmission is unflawed, crs will remain asserted for the duration of the packet, negating just after the last bit has been received. as a packet is coming in, the decoder's carrier sense function monitors the data stream for the end-of-packet symbol, a special non-manchester code element at the end of the packet. upon detecting this symbol, the carrier sense line will be negated. loss of carrier will also result in negation of the carrier sense line, for example, when a collision occurs. receive packet processing as a receive packet comes in from the network, its destination address field is tested for the various address filter criteria selected by the address filter mode bits (af1, af0) and the hash table. see figure 15 for 88023 packet format. only if the address meets the filter criteria selected will the packet be accepted for storage in the receive buffer. in addition, the packet must be error-free, unless the chip has been enabled to receive flawed packets for diagnostic purposes. if these conditions are met, the packet reception results in the packet being stored in the buffer, its 4-byte header being updated at the end of reception, the rx buf empty bit being cleared, the rx pkt bit being set high and an interrupt being generated (if enabled). otherwise the packet will be discarded and pointers will be reset to reuse the same portion of memory for the next packet to arrive. if a flawed packet is accepted for storage for diagnostic purposes, its error(s) will be reported in the pkt status byte of its header (refer to table 3 for byte and bit positions). figure 15. 88023 packet format 8662 4 destination address preamble source address length/type data 461500 crc note: (lengths shown in bytes) end of preamble bit pattern end of packet symbol
mb86960 network management error, traffic and performance statistics can be collected continuously or on a sampled basis. the receive status register and transmit status register indicate any errors detected. such data can be collected in two ways. either interrupts can be used after each packet, and the status read from the status register by the interrupt service routine, or, for the receive case, the packets can be accepted for storage in the receive buffer, allowing their contents and error statuses (stored in the header) to be read later in batch mode. to get maximum statistics for the network, the aaccept all packetso mode can be used. in this mode, all packets can be counted, including their lengths. but of course, this use will maximize host overhead, so it should be used sparingly in user terminal equipment. carrier detection can be sampled as a means of estimating network bandwidth utilization. this bit is available in the transmit status register (net bsy). an estimate of the average media-access waiting time can be calculated from the elapsed time between starting the transmitter and tx done going high. the transmit collision count (dlcr4<7:4>) can be used to determine the number of collisions encountered by the last outgoing packet. (the counter is reset at the start of transmitting each new packet.)
mb86960 electrical characteristics table 17. absolute maximum ratings symbol parameter description min. max. units v cc supply voltage 0.5 6.0 v v in input voltage 0.5 v cc + 0.5 v v out output voltage 0.5 v cc + 0.5 v i odf differential output current on txdata pins 40 ma v idc input dc voltage on rxdata and col 0.5 16 v v odc1 output dc voltage on txdata w/o transformer 0.5 14 v v odc2 output dc voltage on txdata with transformer 0.5 16 v t bias temperature under bias 25 +85 c t stg storage temperature 40 +125 c pwr power dissipation 425 mw 1. permanent device damage may occur if absolute maximum ratings are exceeded. exposure to absolute maximum rating conditions for extended periods may affect device reliability. 2. not more than one output may be shorted to ground or v cc at a time for a maximum duration of one second. table 18. recommended operating conditions symbol parameter description min. typ. max. units v dd supply voltage 4.75 5.25 v v ih logic input high voltage 2.2 v v il logic input low voltage 0.8 v r l driver load resistors on txdata pins to ground 250 270 290 ohm r t termination resistors (2 in series across rxdata and col ) 38.6 39 39.4 ohm c t termination bypass capacitors (between junction of termination resistors and ground) 0.1 f c osc oscillator load capacitance, including stray capacitance (see figure 3) 12 20 38 pf f xtal crystal oscillator frequency 19.999 20 20.001 mhz t a operating temperature 0 70 c
mb86960 table 19. dc specifications (at recommended operating conditions unless otherwise noted.) symbol parameter description conditions min. typ. max. units v il low level input voltage 0.0 0.8 v v ih high level input voltage 2.2 v cc v v ol1 low level output voltage, all outputs except dreq i ol = 3.2 ma 0.0 0.4 v v ol2 low level output voltage, dreq only i ol = 12 ma 0.0 0.4 v v oh1 high level output voltage, all outputs except dreq i oh = +2 ma 4.2 v cc v v oh2 high level output voltage, dreq only i oh = +4 ma 4.2 v cc v v op txdata peak output r l = 270 ohms 0.5 1.3 v v accm output ac common mode on txdata r l = 270 ohms, r t = 78 ohms 40 mv v dccm output dc common mode on txdata r l = 270 ohms 2.4 3.4 4.4 v v sq squelch threshold ac/dc = 1 ac/dc = 0 300 80 220 0 140 +80 mv mv i l input leakage current v i = 0 v cc 10 10 a i pwrdn power down v cc current no output loads 6 10 ma i cc operating v cc current no output loads 40 85 ma table 20. general capacitance (t a = 25 c, v dd = v i = 0 v, f = 1 mhz) symbol parameter description min. max. units c in input pin capacitance 16 pf c out output pin capacitance 16 pf c i/o i/o pin capacitance 16 pf
mb86960 t 1 t 3 t 2 t 5 t 4 t 6 t 9 t 8 t 7 t 10 sa0-3 cs rd rdy rdy sd15-0 (from nice) t 11 figure 16. read cycle tristate tristate tristate tristate table 21. read cycle symbol parameter description min. max. units t 1 cs low to rd low; sa30 valid to rd low 3 ns t 2 rd high to cs high; rd high to sa30 invalid 3 ns t 3 rd low pulse width 30 ns t 4 rd low to rdy low 0 26 ns t 5 rd low to rdy tristate [1] 175 ns t 6 rd low to rdy low [2] 0 175 ns t 7 rd high to rdy tristate 28 ns t 8 rd low to sd150 valid (except buffer memory port) 44 ns t 9 rdy tristate to sd150 valid (buffer port) 8 ns t 10 rdy low to sd150 valid 10 ns t 11 rd high to sd150 invalid (data hold) 15 ns 1. 0 ns maximum for registers, and for buffer memory port when port is ready before the read cycle begins. for port access only, 175 ns maximum may occur if system makes contiguous system read cycles at less than 100 ns intervals, and both the transmitter and receiver are active in aloopbacko reception. 2.15 m s max for bus read error. 2. 28 ns maximum for all registers. for port access only, 175 ns maximum may occur if system makes contiguous system read cycles at less than 100 ns intervals, and both the transmitter and receiver are active in aloopbacko reception. 2.15 m s max for bus read error.
mb86960 t 1 t 3 t 2 t 5 t 4 t 6 t 9 t 8 t 7 sa0-3 cs rd rdy rdy sd15-0 (to nice) figure 17. write cycle tristate tristate tristate tristate table 22. write cycle symbol parameter description min. max. units t 1 cs low to we low; sa30 valid to we low 3 ns t 2 we high to cs high; we high to sa30 invalid 3 ns t 3 we low pulse width 36 ns t 4 we low to rdy low 0 26 ns t 5 we low to rdy tristate [1] 175 ns t 6 we low to rdy low [2] 0 175 ns t 7 we high to rdy tristate 28 ns t 8 sd150 valid to we high (data setup) 5 ns t 9 we high to sd150 invalid (data hold) 6 ns 1. 0 ns maximum for registers, and for buffer memory port when port is ready before the write cycle begins. for port access only, 175 ns maximum may occur if system makes contiguous system write cycles at less than 100 ns intervals, and both the transmitter and receiver are active in aloopbacko reception. 2. 28 ns maximum for all registers. for port access only, 175 ns maximum may occur if system makes contiguous system write cycles at less than 100 ns intervals, and both the transmitter and receiver are active in aloopbacko reception.
mb86960 t 1 t 3 t 2 t 5 t 4 t 6 t 7 dreq dack rd or we rdy rdy eop figure 18. single-cycle dma timing tristate tristate tristate tristate table 23. single-cycle dma timing symbol parameter description min. max. units t 1 dack low to dreq low 0 21 ns t 2 dack high to dreq high 0 19 ns t 3 dack low to rd or we low 0 ns t 4 rd or we high to dack high 3 ns t 5 rd or we low to eop low 0 ns t 6 eop high to dack high 3 ns t 7 eop low pulse width 10 ns 1. an asserted eop terminates any further dreq after dack returns high. 2. the dma cycle uses dack as the chip select. dack overrides cs and sa3-0 if they are both asserted at the same time, forcing selection of the buffer memory port as in a dma cycle. 3. for rdy (rdy) timing and sd15-0 timing, see figure 16, t 4 -t 11 , and figure 17, t 4 -t 9 .
mb86960 figure 19. burst dma timing dack dreq rd or we rdy rdy tristate tristate t 1 t 2 table 24. burst dma timing symbol parameter description min. max. units t 1 rd or we low to dreq low 32 ns t 2 rd or we high to dack high 3 ns 1. dreq goes low during the next-to-last transfer of the burst. dack should not go high until after the rd or we pulse of the last transfer cycle goes high. 2. the dma cycle uses dack as the chip select. dack overrides cs and sa3-0 if they are both asserted at the same time, forcing selection of the buffer memory port as in a dma cycle. 3. for rdy (rdy) timing and sd15-0 timing, see figure 16, t 4 -t 11 , and figure 17, t 4 -t 9 .
mb86960 figure 20. burst dma interrupted by dack dack dreq rd or we rdy rdy burst interrupted tristate tristate notes: burst can be interrupted by dack high-going pulse during the burst. burst will resume when dack returns low.
mb86960 figure 21. burst dma terminated by eop dack dreq eop t 1 t 2 t 3 rd or we table 25. burst dma terminated by eop symbol parameter description min. max. units t 1 eop low to dreq low 4 28 ns t 2 eop high to dack high 3 ns t 3 rd or we low to eop low 0 ns note: eop can be asserted during any transfer of the burst to terminate the process following that transfer.
mb86960 figure 22. reset timing cs reset t 1 t 2 table 26. reset timing symbol parameter description min. max. units t 1 reset pulse width 200 ns t 2 reset low to first cs low 300 ns note: before enabling transmit and receive functions (dlc en ), wait 200 m s after reset pulse for stabilization of receiver pll. figure 23. skip packet timing we t 1 cs rd table 27. skip packet timing symbol parameter description min. max. units t 1 writing skip packet high to next buffer memory port read 300 ns
mb86960 t 1 t 3 t 2 t 4 lbc we cntrl ten int figure 24. lbc, cntrl , and int timing table 28. lbc cntrl and int timing symbol parameter description min. typ. max. units t 1 loopback control (lbc) delay 20 60 ns t 2 cntrl delay 20 60 ns t 3 int signal clearing delay 20 60 ns t 4 transmit enable delay after setting tx start high (if network free) 2.3 s
mb86960 t 1 t 3 t 2 t 5 t 4 t 6 t 8 t 7 ba15-0 bcs1,0 boe bd15-0 figure 25. sram read timing table 29. sram read timing symbol parameter description min. max. units t 1 read cycle 95 ns t 2 address access time 81 ns t 3 address valid to bcs1,0 low 0 8 ns t 4 bcs1,0 high to address invalid 0 ns t 5 chip select access time 81 ns t 6 boe high to bcs1,0 high 0 2 ns t 7 output enable access time 49 ns t 8 data hold time 0 ns note: use sram with address access time of 80 ns or less.
mb86960 t 1 t 3 t 2 t 4 t 8 t 11 t 10 ba15-0 bcs1,0 bwe bd15-0 figure 26. sram write timing t 5 t 9 t 6 t 7 table 30. sram write timing symbol parameter description min. max. units t 1 write cycle 95 ns t 2 address valid to bcs1,0 low 2 8 ns t 3 address valid to bwe high 71 ns t 4 bcs1,0 low to bwe high 62 ns t 5 bcs1,0 high to address invalid 0 ns t 6 bcs1,0 low to bwe low 0 ns t 7 bwe pulse width 60 ns t 8 bwe high to bcs1,0 high 0 ns t 9 bwe high to address invalid 12 ns t 10 data setup time 41 ns t 11 data hold time 14 ns note: use sram with address access time of 80 ns or less.
mb86960 figure 27. transmit timing int ten t1 t2 t4 t13 t6 t5 (if it is enabled) 1st bit last bit txd tck t3 figure 28. transmit timing col ten t7 t9 t8 figure 29. transmit timing txd ten col int t10 preamble t11p start jam
mb86960 figure 30. transmit timing txd ten col int jam t 10 t 11p /t 11d t 12 table 31. transmit timing: figures 2730 (for encoder/decoder bypass mode) symbol description min. typ. max. units t 1 transmit clock low width 40 50 60 ns t 2 transmit clock high width 40 50 60 ns t 3 ten high to tck low 48 e e ns t 4 transmit data hold 12 e e ns t 5 tck low to ten low 13 e e ns t 6 transmit interrupt low to transmit enable low e 1 e tck cycles t 7 collision low pulse width 20 e e ns t 8 collision high pulse width e e 200 ns t 9 minimum collision length 520 e e ns t 10 jam period [1] e 32 e tck cycles t 11p transmit interrupt when collision at preamble e 5 e tck cycles t 11d transmit interrupt when collision at data field e 16 e tck cycles t 12 collision to first jam bit 4 e 12 tck cycles t 13 transmit data setup 40 e e ns 1. the 32 jam bits include eight data bits and 24 `0' bits.
mb86960 figure 31. transmit start timing t1 txdata+ ten txdata txdata txd t2 t3 t4 t5 t6 t 7 t 8 101 0 101 note: if ac/dc = low tck
mb86960 figure 32. transmit end timing txdata+ ten txdata txdata (if last bit=0) txd t4 t5 1 0(1) 0 01 note: if ac/dc = low tck 0 1 01 t9 t10 txdata (if last bit=1) table 32. transmit start and end timing: figures 3132 (for encoder/decoder test mode) symbol figure parameter description conditions min. typ. max. units t 1 31 tck cycle time 99.99 100 100.01 ns t 2 31 tck high width 35 50 65 ns t 3 31 tck low width 35 50 65 ns t 4 31, 32 txd, ten setup time to tck 20 e e ns t 5 31, 32 txd, ten hold time from tck 10 e e ns t 6 31 txdata encode time e 95 e ns t 7 31 txdata fall time 20% to 80% e 2 e ns t 8 31 txdata rise time 20% to 80% e 2 e ns t 9 32 txdata line voltage transition ac/dc = high e e 8000 ns t 10 32 txdata end-of-packet delimiter ac/dc = high 200 e e ns
mb86960 0 figure 33. loopback timing lbc tck t 2 t 4 t 5 t 1 t 3 1 0 1 1 0 txd ten crs rxd rck 67 clock inhibit 1 clock inhibit table 33. loopback timing (for encoder/decoder bypass mode) symbol parameter description min. typ. max. units t 1 lbc receiving data purge time e 260 e ns t 2 wait time from crs low to ten high 9.6 e e s t 3 data through time e 280 e ns t 4 txd, ten setup to me to tck 0 e e ns t 5 lbc receiving data accept time e 80 e ns
mb86960 figure 34. collision timing col t 6 t 7 col note: if ac/ldc = low table 34. collision timing (for encoder/decoder test mode) symbol parameter description min. typ. max. units t 6 ,t 7 col to col propagation delay time 15 50 e ns
mb86960 figure 35. receive timing crs rck t 2 t 5 t 1 t 3 rxd t 4 t 7 t 8 (if it is not masked) 1st bit last bit t 5 int table 35. receive timing (for encoder/decoder bypass mode) symbol parameter description min. typ. max. units t 1 receive clock low width 35 ns t 2 receive clock high width 35 ns t 3 receive data setup 10 ns t 4 receive data hold 10 ns t 5 receive carrier sense setup 10 ns t 6 receive carrier sense hold 7 rck cycles t 7 last bit of good packet received to interrupt 40 rck cycles t 8 receive interrupt after bad packet 15 rck cycles
mb86960 figure 36. receive start timing rxdata crs t1 67 clock inhibit 1010 1 01 8th rising edge t2 t3 t4 t5 rxd note: if ac/dc = low t6 t7 rck
mb86960 figure 37. receive end timing crs t 7 rxdata note: if ac/dc = low t 6 t 8 t 11 t 9 t 10 10 0 1 10 0 1 rck rxd table 36. receive timing: figures 3637 (for encoder/decoder test mode) symbol figure parameter description conditions min. typ. max. units t 1 36 crs on delay time e 90 120 ns t 2 36 crs low hold time 10 e e ns t 3 36 rck delay time e 125 e ns t 4 36 rck high time 35 50 e ns t 5 36 rck low time 35 50 e ns t 6 36, 37 rxd setup time to rck 20 60 e ns t 7 36, 37 rxd hold time from rck 10 20 e ns t 8 37 crs off delay time e 260 e ns t 9 37 crs high hold time e 130 e ns t 10 37 crs low setup time e 70 e ns t 11 37 rck cycle time during idle 99.99 100 100.01 ns
mb86960 figure 38. test conditions 270 w 78 w 270 w txdata output load 60 pf ttl output load ttl input waveform txdata output waveform [(txdata+) (txdata)] rxdata , col , input waveform test point = 3.0 v vih = 3.5 v vil = 2.5 v test point = 50% test point = 1.5 v vih = 2.2 v vil = 0.8 v test point = 1.5 v voh = 2.0 v vol = 1.0 v ttl output waveform
mb86960 100-pin plastic flat package ordering information: MB86960APF-G 100-lead plastic flat package (case no. fpt-100p-m06)

▲Up To Search▲

Price & Availability of MB86960APF-G

	To Download MB86960APF-G Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .